From: David Miller <davem@davemloft.net>
To: jeffrey.t.kirsher@intel.com
Cc: netdev@vger.kernel.org, gospo@redhat.com,
peter.p.waskiewicz.jr@intel.com
Subject: Re: [net-next-2.6 PATCH v5 0/3] Introduce n-tuple ethtool support
Date: Wed, 10 Feb 2010 20:01:44 -0800 (PST) [thread overview]
Message-ID: <20100210.200144.142835867.davem@davemloft.net> (raw)
In-Reply-To: <20100210.195445.190157100.davem@davemloft.net>
From: David Miller <davem@davemloft.net>
Date: Wed, 10 Feb 2010 19:54:45 -0800 (PST)
> All applied, thanks.
Guys please check your changes for warnings in the build:
net/core/dev.c: In function ‘free_netdev’:
net/core/dev.c:5452: warning: unused variable ‘f’
net/core/dev.c:5452: warning: unused variable ‘fsc’
CC [M] drivers/net/e1000e/lib.o
CC [M] drivers/net/e1000e/phy.o
CC net/core/ethtool.o
CC [M] drivers/net/e1000e/param.o
net/core/ethtool.c: In function ‘ethtool_reset’:
net/core/ethtool.c:626: warning: unused variable ‘f’
net/core/ethtool.c:626: warning: unused variable ‘fsc’
net/core/ethtool.c: In function ‘ethtool_nway_reset’:
net/core/ethtool.c:676: warning: unused variable ‘f’
net/core/ethtool.c:676: warning: unused variable ‘fsc’
I'll fix this up, but you know... :-/
next prev parent reply other threads:[~2010-02-11 4:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 2:07 [net-next-2.6 PATCH v5 0/3] Introduce n-tuple ethtool support Jeff Kirsher
2010-02-11 2:07 ` [net-next-2.6 PATCH v5 1/3] ethtool: Introduce n-tuple filter programming support Jeff Kirsher
2010-02-11 2:07 ` [net-next-2.6 PATCH v5 2/3] ixgbe: Add support for the new ethtool n-tuple programming interface Jeff Kirsher
2010-02-11 2:08 ` [net-next-2.6 PATCH v5 3/3] ixgbe: Bump driver version up Jeff Kirsher
2010-02-11 3:54 ` [net-next-2.6 PATCH v5 0/3] Introduce n-tuple ethtool support David Miller
2010-02-11 4:01 ` David Miller [this message]
2010-02-11 4:18 ` Peter P Waskiewicz Jr
2010-02-14 11:56 ` includes build break - was " Oliver Hartkopp
2010-02-15 6:38 ` David Miller
2010-02-11 8:02 ` robert
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=20100210.200144.142835867.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.com \
/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).