Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [next PATCH 1/3] igb: Enable the ethtool interface fo Rx filter
Date: Thu, 24 Dec 2015 14:02:43 -0800	[thread overview]
Message-ID: <1450994563.3316.42.camel@intel.com> (raw)
In-Reply-To: <1450925102-28992-2-git-send-email-gangfeng.huang@ni.com>

On Thu, 2015-12-24 at 10:45 +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??? |?? 57 ++++++++
> ?3 files changed, 281 insertions(+)

Still does not apply cleanly, are you sure you are using the dev-queue
branch of mt next-queue tree?

Here is what I get when I try to apply it by hand:
[13:53:24 @jtkirshe-linux:next-queue]$ patch -p1 <.apply/next-1-3-igb-
Enable-the-ethtool-interface-fo-Rx-filter.patch?
patching file drivers/net/ethernet/intel/igb/igb.h
Hunk #1 succeeded at 353 (offset 5 lines).
Hunk #2 FAILED at 476.
Hunk #3 succeeded at 612 (offset 17 lines).
1 out of 3 hunks FAILED -- saving rejects to file
drivers/net/ethernet/intel/igb/igb.h.rej
patching file drivers/net/ethernet/intel/igb/igb_ethtool.c
Hunk #1 succeeded at 2607 (offset 186 lines).
Hunk #2 succeeded at 2702 (offset 186 lines).
Hunk #3 succeeded at 2826 (offset 186 lines).
Hunk #4 succeeded at 2971 (offset 186 lines).
patching file drivers/net/ethernet/intel/igb/igb_main.c
Hunk #1 succeeded at 188 with fuzz 2 (offset 12 lines).
Hunk #2 succeeded at 1636 (offset 23 lines).
Hunk #3 succeeded at 2085 (offset 26 lines).
Hunk #4 succeeded at 2448 with fuzz 1 (offset 47 lines).
Hunk #5 FAILED at 2996.
Hunk #6 succeeded at 3259 (offset 77 lines).
Hunk #7 FAILED@8135.
2 out of 7 hunks FAILED -- saving rejects to file
drivers/net/ethernet/intel/igb/igb_main.c.rej

Make sure you are running `git branch -b origin/dev-queue` after
cloning my next-queue tree.

Dropping this series and will await an updated series.
-------------- 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/20151224/22b20ffa/attachment-0001.asc>

  reply	other threads:[~2015-12-24 22:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-24  2:44 [Intel-wired-lan] [next PATCH 0/3] igb: add Rx ethertype filter and VLAN priority filter Gangfeng
2015-12-24  2:45 ` [Intel-wired-lan] [next PATCH 1/3] igb: Enable the ethtool interface fo Rx filter Gangfeng
2015-12-24 22:02   ` Jeff Kirsher [this message]
2015-12-24  2:45 ` [Intel-wired-lan] [next PATCH 2/3] igb: add support of ethertype RX filters Gangfeng
2015-12-24  2:45 ` [Intel-wired-lan] [next PATCH 3/3] igb: add support of Rx VLAN priority filters Gangfeng

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=1450994563.3316.42.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