From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH 1/3] igb: Enable the ethtool interface fo Rx filter
Date: Wed, 24 Feb 2016 12:29:33 -0800 [thread overview]
Message-ID: <1456345773.2808.8.camel@intel.com> (raw)
In-Reply-To: <1456304783-15019-1-git-send-email-gangfeng.huang@ni.com>
On Wed, 2016-02-24 at 17:06 +0800, Gangfeng wrote:
> From: Gangfeng Huang <gangfeng.huang@ni.com>
>
> This patch is meant to allow for nfc to insert and remove Rx filter
> by ethtool. Ethtool interface has it's own rules manager
>
> Show all filters:
> $ ethtool -n eth0
> 4 RX rings available
> Total 2 rules
>
> Signed-off-by: Ruhao Gao <ruhao.gao@ni.com>
> Signed-off-by: Gangfeng Huang <gangfeng.huang@ni.com>
> ---
> ?drivers/net/ethernet/intel/igb/igb.h???????? |?? 31 +++++
> ?drivers/net/ethernet/intel/igb/igb_ethtool.c |? 193
> ++++++++++++++++++++++++++
> ?drivers/net/ethernet/intel/igb/igb_main.c??? |?? 45 ++++++
> ?3 files changed, 269 insertions(+)
What does NFC mean? ?It is proper etiquette to spell out all acronyms
before using them, especially when they are not universally known.
Did you address Aaron Brown questions and concerns? ?I do not see any
change log to this series of patches, so I do not think you changed
anything from the first time you submitted it. ?I rejected this the
first time around because of the questions and concerns Aaron brought
up, so if you are going to ignore Aaron, you might as well forget about
getting these changes into the kernel.
Also for the amount of changes you are making to the igb, we will need
a clearly defined justification as to why this is needed. ?Your sparse
patch description needs more information to help us understand why we
need these changes.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.osuosl.org/pipermail/intel-wired-lan/attachments/20160224/17739957/attachment.asc>
next prev parent reply other threads:[~2016-02-24 20:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 9:06 [Intel-wired-lan] [PATCH 1/3] igb: Enable the ethtool interface fo Rx filter Gangfeng
2016-02-24 9:06 ` [Intel-wired-lan] [PATCH 2/3] igb: add support of ethertype RX filters Gangfeng
2016-02-24 9:06 ` [Intel-wired-lan] [PATCH 3/3] igb: add support of Rx VLAN priority filters Gangfeng
2016-02-24 20:29 ` Jeff Kirsher [this message]
2016-02-25 2:52 ` [Intel-wired-lan] [PATCH 1/3] igb: Enable the ethtool interface fo Rx filter Gangfeng Huang
-- strict thread matches above, loose matches on Subject: below --
2015-12-22 6:59 [Intel-wired-lan] [PATCH 0/3] igb: Add RX ethertype filter and VLAN priority filter Gangfeng Huang
2015-12-22 6:59 ` [Intel-wired-lan] [PATCH 1/3] igb: Enable the ethtool interface fo Rx filter Gangfeng Huang
2015-12-21 6:40 [Intel-wired-lan] [PATCH 0/3] igb: add RX ethertyp filter and VLAN priority filter Gangfeng Huang
2015-12-21 6:40 ` [Intel-wired-lan] [PATCH 1/3] igb: Enable the ethtool interface fo Rx filter Gangfeng Huang
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=1456345773.2808.8.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=intel-wired-lan@osuosl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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