From: Or Gerlitz <ogerlitz@mellanox•com>
To: "Vick, Matthew" <matthew.vick@intel•com>
Cc: Jeff Kirsher <jeffrey.t.kirsher@intel•com>,
"netdev@vger•kernel.org" <netdev@vger•kernel.org>
Subject: Re: [PATCH net-next] net/fm10k: Avoid double setting of NETIF_F_SG for the HW encapsulation feature mask
Date: Sun, 9 Nov 2014 10:15:05 +0200 [thread overview]
Message-ID: <545F2289.1090802@mellanox.com> (raw)
In-Reply-To: <D0827E2E.5ED4E%matthew.vick@intel.com>
On 11/7/2014 11:57 PM, Vick, Matthew wrote:
> Good catch, Or! Thank you for taking care of this!
sure
> Someone can correct me if I'm mistaken (I thought checkpatch would
> complain about this, but it doesn't seem to be), but I believe the start
> of the lines should match up like they are for the dev->features. Would
> you like to submit a V2 with this change or would you like me to do it
> (giving you credit via your Reported-by)?
I just submitted V1 along your request
prev parent reply other threads:[~2014-11-09 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 9:21 [PATCH net-next] net/fm10k: Avoid double setting of NETIF_F_SG for the HW encapsulation feature mask Or Gerlitz
2014-11-06 21:44 ` David Miller
2014-11-07 6:44 ` Jeff Kirsher
2014-11-07 21:57 ` Vick, Matthew
2014-11-09 8:15 ` Or Gerlitz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=545F2289.1090802@mellanox.com \
--to=ogerlitz@mellanox$(echo .)com \
--cc=jeffrey.t.kirsher@intel$(echo .)com \
--cc=matthew.vick@intel$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox