[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20171105.220843.222678154572186350.davem@davemloft.net>
Date: Sun, 05 Nov 2017 22:08:43 +0900 (KST)
From: David Miller <davem@...emloft.net>
To: kurup.manish@...il.com
Cc: jhs@...atatu.com, xiyou.wangcong@...il.com, jiri@...nulli.us,
jakub.kicinski@...ronome.com, pieter.jansenvanvuuren@...ronome.com,
simon.horman@...ronome.com, john.hurley@...ronome.com,
oss-drivers@...ronome.com, netdev@...r.kernel.org,
aring@...atatu.com, mrv@...atatu.com, manish.kurup@...izon.com
Subject: Re: [PATCH net-next v6 0/3] Incorporated all required changes
From: Manish Kurup <kurup.manish@...il.com>
Date: Fri, 3 Nov 2017 11:49:19 -0400
> Modified the netronome drivers (flower action) to use the VLAN helper
> functions instead of dereferencing the structure directly. This is
> required for the VLAN action patch.
>
> Could you please review?
Please use a more appropriate patch series header posting than this.
This subject shall describe what the patch series is about, in much
the same style as a normal commit, using appropriate subsystem
prefixes and so on.
The commit message body must describe what the patch series is doing,
how it is doing it, and why it is doing it that way.
Powered by blists - more mailing lists