From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Joe Perches <joe@perches.com>
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
Bruce Allan <bruce.w.allan@intel.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
linux-kernel@vger.kernel.org,
John Ronciak <john.ronciak@intel.com>,
Brice Goglin <brice@myri.com>,
Andrew Gallatin <gallatin@myri.com>,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH net-next 0/7] drivers/net conversions to netdev_<level>, etc
Date: Tue, 23 Feb 2010 18:33:23 -0800 [thread overview]
Message-ID: <9929d2391002231833j65008a1ev1d2297672a39a483@mail.gmail.com> (raw)
In-Reply-To: <cover.1266893507.git.joe@perches.com>
On Mon, Feb 22, 2010 at 18:56, Joe Perches <joe@perches.com> wrote:
> Some more conversions of drivers to:
>
> netif_<level>
> netdev_<level>
> pr_<level>
>
> with some other minor updates/corrections
> noticed during conversions.
>
> Joe Perches (7):
> drivers/net/chelsio: Use pr_<level>, netif_msg_<type>
> drivers/net/myri10ge: Use pr_<level> and netdev_<level>
> drivers/net/ixgbe: Use pr_<level> and netif_<level>
> drivers/net/ixgb: Use pr_<level> and netdev_<level>
> drivers/net/e1000: Use pr_<level> and netif_<level>
> drivers/net/e1000e: Use pr_<level> and netdev_<level>
> drivers/net/igb: Use netdev_<level>
>
> drivers/net/chelsio/common.h | 24 +--
> drivers/net/chelsio/cxgb2.c | 18 +-
> drivers/net/chelsio/espi.c | 4 +-
> drivers/net/chelsio/pm3393.c | 16 +-
> drivers/net/chelsio/sge.c | 10 +-
> drivers/net/chelsio/subr.c | 32 ++--
> drivers/net/chelsio/vsc7326.c | 24 ++--
> drivers/net/e1000/e1000.h | 17 --
> drivers/net/e1000/e1000_ethtool.c | 38 ++--
> drivers/net/e1000/e1000_hw.c | 383 ++++++++++++++++++-------------------
> drivers/net/e1000/e1000_main.c | 272 +++++++++++++-------------
> drivers/net/e1000/e1000_osdep.h | 14 +--
> drivers/net/e1000/e1000_param.c | 121 +++++++------
> drivers/net/e1000e/82571.c | 57 ++++--
> drivers/net/e1000e/e1000.h | 21 --
> drivers/net/e1000e/es2lan.c | 27 ++--
> drivers/net/e1000e/ethtool.c | 37 ++--
> drivers/net/e1000e/ich8lan.c | 90 +++++----
> drivers/net/e1000e/lib.c | 131 +++++++-------
> drivers/net/e1000e/netdev.c | 95 +++++-----
> drivers/net/e1000e/param.c | 20 +-
> drivers/net/e1000e/phy.c | 114 ++++++------
> drivers/net/igb/e1000_82575.c | 58 +++---
> drivers/net/igb/e1000_hw.h | 12 +-
> drivers/net/igb/e1000_mac.c | 84 ++++----
> drivers/net/igb/e1000_nvm.c | 22 +-
> drivers/net/igb/e1000_phy.c | 104 +++++-----
> drivers/net/igb/igb.h | 1 -
> drivers/net/igb/igb_ethtool.c | 6 +-
> drivers/net/igb/igb_main.c | 43 ++---
> drivers/net/ixgb/ixgb.h | 8 +-
> drivers/net/ixgb/ixgb_ee.c | 14 +-
> drivers/net/ixgb/ixgb_hw.c | 147 ++++++---------
> drivers/net/ixgb/ixgb_hw.h | 12 --
> drivers/net/ixgb/ixgb_main.c | 33 ++--
> drivers/net/ixgb/ixgb_osdep.h | 16 +--
> drivers/net/ixgb/ixgb_param.c | 31 ++--
> drivers/net/ixgbe/ixgbe.h | 6 -
> drivers/net/ixgbe/ixgbe_common.h | 15 +-
> drivers/net/ixgbe/ixgbe_dcb_nl.c | 5 +-
> drivers/net/ixgbe/ixgbe_ethtool.c | 40 +++--
> drivers/net/ixgbe/ixgbe_fcoe.c | 25 ++--
> drivers/net/ixgbe/ixgbe_main.c | 110 +++++------
> drivers/net/ixgbe/ixgbe_phy.c | 2 +
> drivers/net/ixgbe/ixgbe_sriov.c | 11 +-
> drivers/net/myri10ge/myri10ge.c | 183 +++++++-----------
> 46 files changed, 1202 insertions(+), 1351 deletions(-)
>
I have applied patches 3-7 (the patches to Intel drivers) to my queue
of patches for review and testing.
--
Cheers,
Jeff
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
next prev parent reply other threads:[~2010-02-24 2:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 2:56 [PATCH net-next 0/7] drivers/net conversions to netdev_<level>, etc Joe Perches
2010-02-23 2:56 ` [PATCH net-next 1/7] drivers/net/chelsio: Use pr_<level>, netif_msg_<type> Joe Perches
2010-02-26 9:40 ` David Miller
2010-02-23 2:56 ` [PATCH net-next 2/7] drivers/net/myri10ge: Use pr_<level> and netdev_<level> Joe Perches
2010-02-26 9:40 ` David Miller
2010-02-23 2:56 ` [PATCH net-next 3/7] drivers/net/ixgbe: Use pr_<level> and netif_<level> Joe Perches
2010-02-23 2:57 ` [PATCH net-next 4/7] drivers/net/ixgb: Use pr_<level> and netdev_<level> Joe Perches
2010-02-23 2:57 ` [PATCH net-next 5/7] drivers/net/e1000: Use pr_<level> and netif_<level> Joe Perches
2010-02-23 2:57 ` [PATCH net-next 6/7] drivers/net/e1000e: Use pr_<level> and netdev_<level> Joe Perches
2010-02-23 19:17 ` Allan, Bruce W
2010-02-23 2:57 ` [PATCH net-next 7/7] drivers/net/igb: Use netdev_<level> Joe Perches
2010-02-24 2:33 ` Jeff Kirsher [this message]
2010-03-01 21:16 ` [PATCH net-next] drivers/net/e100.c: Use pr_<level> and netif_<level> Joe Perches
2010-03-17 4:31 ` David Miller
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=9929d2391002231833j65008a1ev1d2297672a39a483@mail.gmail.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=brice@myri.com \
--cc=bruce.w.allan@intel.com \
--cc=davem@davemloft.net \
--cc=e1000-devel@lists.sourceforge.net \
--cc=gallatin@myri.com \
--cc=jesse.brandeburg@intel.com \
--cc=joe@perches.com \
--cc=john.ronciak@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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).