From: Jeff Garzik <jgarzik@pobox.com>
To: Jim Lewis <jklewis@us.ibm.com>
Cc: akpm@osdl.org, netdev@vger.kernel.org
Subject: Re: [PATCH] Spidernet: add ethtool -S (show statistics)
Date: Fri, 22 Sep 2006 20:13:10 -0400 [thread overview]
Message-ID: <45147C16.4020608@pobox.com> (raw)
In-Reply-To: <1158865352.30496.29.camel@lewis2.austin.ibm.com>
ACK, but patch does not apply:
Applying 'Spidernet: add ethtool -S (show statistics)'
error: patch fragment without header at line 14: @@ -472,6 +472,7 @@
spider_net_prepare_rx_descr(struct spide
error: patch fragment without header at line 22: @@ -492,6 +493,7 @@
spider_net_prepare_rx_descr(struct spide
error: patch fragment without header at line 30: @@ -721,6 +723,7 @@
spider_net_prepare_tx_descr(struct spide
error: patch fragment without header at line 38: @@ -942,6 +945,7 @@
spider_net_xmit(struct sk_buff *skb, str
error: patch fragment without header at line 47: @@ -1047,6 +1051,7 @@
spider_net_pass_skb_up(struct spider_net
error: patch fragment without header at line 55: @@ -1144,9 +1149,11 @@
spider_net_decode_one_descr(struct spide
error: patch fragment without header at line 68: @@ -2112,6 +2119,7 @@
spider_net_tx_timeout(struct net_device
error: patch fragment without header at line 82: @@ -438,6 +438,15 @@
struct spider_net_options {
error: patch fragment without header at line 98: @@ -464,9 +473,9 @@
struct spider_net_card {
error: patch fragment without header at line 115: @@ -27,6 +27,27 @@
error: patch fragment without header at line 143: @@ -143,6 +164,38 @@
spider_net_ethtool_get_ringparam(struct
error: patch fragment without header at line 183: @@ -155,5 +208,8 @@
struct ethtool_ops spider_net_ethtool_op
fatal: No changes
prev parent reply other threads:[~2006-09-23 0:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 19:02 [PATCH] Spidernet: add ethtool -S (show statistics) Jim Lewis
2006-09-23 0:13 ` Jeff Garzik [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=45147C16.4020608@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=jklewis@us.ibm.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).