From: Jean Sacren <sakiwit@gmail.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
linux.nics@intel.com
Subject: [PATCH net-next 0/6] Simplify Intel Wired LAN driver init/exit routine
Date: Tue, 2 Sep 2014 03:36:50 -0600 [thread overview]
Message-ID: <1409650616-1035-1-git-send-email-sakiwit@gmail.com> (raw)
This series uses module_pci_driver() to simplify the init/exit
routine of some Intel Wired LAN drivers.
Jean Sacren (6):
ixgb: remove the boilerplate of ixgb module for init/exit
ixgbevf: remove the boilerplate of ixgbevf module for init/exit
e100: remove the boilerplate of e100 module for init/exit
igbvf: remove the boilerplate of igbvf module for init/exit
e1000e: remove the boilerplate of e1000e module for init/exit
i40evf: remove the boilerplate of i40evf module for init/exit
drivers/net/ethernet/intel/e100.c | 22 ++++---------
drivers/net/ethernet/intel/e1000e/netdev.c | 35 +++-----------------
drivers/net/ethernet/intel/i40evf/i40evf_main.c | 37 +++------------------
drivers/net/ethernet/intel/igbvf/netdev.c | 35 +++-----------------
drivers/net/ethernet/intel/ixgb/ixgb_main.c | 39 +++--------------------
drivers/net/ethernet/intel/ixgbevf/ixgbevf_main.c | 38 ++++------------------
6 files changed, 32 insertions(+), 174 deletions(-)
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
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 reply other threads:[~2014-09-02 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 9:36 Jean Sacren [this message]
2014-09-03 5:17 ` [PATCH net-next 0/6] Simplify Intel Wired LAN driver init/exit routine Jeff Kirsher
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=1409650616-1035-1-git-send-email-sakiwit@gmail.com \
--to=sakiwit@gmail.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux.nics@intel.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).