From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Joe Perches <joe@perches.com>
Cc: e1000-devel <e1000-devel@lists.sourceforge.net>,
Bruce Allan <bruce.w.allan@intel.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
linux-kernel@vger.kernel.org,
Greg Rose <gregory.v.rose@intel.com>,
John Ronciak <john.ronciak@intel.com>,
netdev@vger.kernel.org
Subject: Re: [RFC PATCH net-next] drivers/net Documentation/networking: Create directory intel_wired_lan
Date: Mon, 11 Oct 2010 16:52:59 -0700 [thread overview]
Message-ID: <AANLkTikVKufQRuMGd=cdig7ff4k2aw9Q1FWwMz3pgon-@mail.gmail.com> (raw)
In-Reply-To: <1286743352.11039.165.camel@Joe-Laptop>
On Sun, Oct 10, 2010 at 13:42, Joe Perches <joe@perches.com> wrote:
> Perhaps it's better to move drivers from the very populated
> drivers/net directory into vendor specific directories similar
> to the Atheros approach used for drivers/net/wireless/ath/
>
> Move intel drivers and Documentation to separate directories
> Create drivers/net/intel_wired_lan/Kconfig.<speed> and Makefile
> Modify drivers/net/Kconfig and Makefile
> Update MAINTAINERS
>
> Signed-off-by: Joe Perches <joe@perches.com>
> ---
> .../networking/{ => intel_wired_lan}/e100.txt | 0
> .../networking/{ => intel_wired_lan}/e1000.txt | 0
> .../networking/{ => intel_wired_lan}/igb.txt | 0
> .../networking/{ => intel_wired_lan}/igbvf.txt | 0
> .../networking/{ => intel_wired_lan}/ixgb.txt | 0
> .../networking/{ => intel_wired_lan}/ixgbe.txt | 0
> .../networking/{ => intel_wired_lan}/ixgbevf.txt | 0
> MAINTAINERS | 18 +--
> drivers/net/Kconfig | 214 +-------------------
> drivers/net/Makefile | 8 -
> drivers/net/intel_wired_lan/Kconfig.100 | 25 +++
> drivers/net/intel_wired_lan/Kconfig.1000 | 102 ++++++++++
> drivers/net/intel_wired_lan/Kconfig.10000 | 81 ++++++++
> drivers/net/intel_wired_lan/Makefile | 9 +
> drivers/net/{ => intel_wired_lan}/e100.c | 0
> drivers/net/{ => intel_wired_lan}/e1000/Makefile | 0
> drivers/net/{ => intel_wired_lan}/e1000/e1000.h | 0
> .../{ => intel_wired_lan}/e1000/e1000_ethtool.c | 0
> drivers/net/{ => intel_wired_lan}/e1000/e1000_hw.c | 0
> drivers/net/{ => intel_wired_lan}/e1000/e1000_hw.h | 0
> .../net/{ => intel_wired_lan}/e1000/e1000_main.c | 0
> .../net/{ => intel_wired_lan}/e1000/e1000_osdep.h | 0
> .../net/{ => intel_wired_lan}/e1000/e1000_param.c | 0
> drivers/net/{ => intel_wired_lan}/e1000e/82571.c | 0
> drivers/net/{ => intel_wired_lan}/e1000e/Makefile | 0
> drivers/net/{ => intel_wired_lan}/e1000e/defines.h | 0
> drivers/net/{ => intel_wired_lan}/e1000e/e1000.h | 0
> drivers/net/{ => intel_wired_lan}/e1000e/es2lan.c | 0
> drivers/net/{ => intel_wired_lan}/e1000e/ethtool.c | 0
> drivers/net/{ => intel_wired_lan}/e1000e/hw.h | 0
> drivers/net/{ => intel_wired_lan}/e1000e/ich8lan.c | 0
> drivers/net/{ => intel_wired_lan}/e1000e/lib.c | 0
> drivers/net/{ => intel_wired_lan}/e1000e/netdev.c | 0
> drivers/net/{ => intel_wired_lan}/e1000e/param.c | 0
> drivers/net/{ => intel_wired_lan}/e1000e/phy.c | 0
> drivers/net/{ => intel_wired_lan}/igb/Makefile | 0
> .../net/{ => intel_wired_lan}/igb/e1000_82575.c | 0
> .../net/{ => intel_wired_lan}/igb/e1000_82575.h | 0
> .../net/{ => intel_wired_lan}/igb/e1000_defines.h | 0
> drivers/net/{ => intel_wired_lan}/igb/e1000_hw.h | 0
> drivers/net/{ => intel_wired_lan}/igb/e1000_mac.c | 0
> drivers/net/{ => intel_wired_lan}/igb/e1000_mac.h | 0
> drivers/net/{ => intel_wired_lan}/igb/e1000_mbx.c | 0
> drivers/net/{ => intel_wired_lan}/igb/e1000_mbx.h | 0
> drivers/net/{ => intel_wired_lan}/igb/e1000_nvm.c | 0
> drivers/net/{ => intel_wired_lan}/igb/e1000_nvm.h | 0
> drivers/net/{ => intel_wired_lan}/igb/e1000_phy.c | 0
> drivers/net/{ => intel_wired_lan}/igb/e1000_phy.h | 0
> drivers/net/{ => intel_wired_lan}/igb/e1000_regs.h | 0
> drivers/net/{ => intel_wired_lan}/igb/igb.h | 0
> .../net/{ => intel_wired_lan}/igb/igb_ethtool.c | 0
> drivers/net/{ => intel_wired_lan}/igb/igb_main.c | 0
> drivers/net/{ => intel_wired_lan}/igbvf/Makefile | 0
> drivers/net/{ => intel_wired_lan}/igbvf/defines.h | 0
> drivers/net/{ => intel_wired_lan}/igbvf/ethtool.c | 0
> drivers/net/{ => intel_wired_lan}/igbvf/igbvf.h | 0
> drivers/net/{ => intel_wired_lan}/igbvf/mbx.c | 0
> drivers/net/{ => intel_wired_lan}/igbvf/mbx.h | 0
> drivers/net/{ => intel_wired_lan}/igbvf/netdev.c | 0
> drivers/net/{ => intel_wired_lan}/igbvf/regs.h | 0
> drivers/net/{ => intel_wired_lan}/igbvf/vf.c | 0
> drivers/net/{ => intel_wired_lan}/igbvf/vf.h | 0
> drivers/net/{ => intel_wired_lan}/ixgb/Makefile | 0
> drivers/net/{ => intel_wired_lan}/ixgb/ixgb.h | 0
> drivers/net/{ => intel_wired_lan}/ixgb/ixgb_ee.c | 0
> drivers/net/{ => intel_wired_lan}/ixgb/ixgb_ee.h | 0
> .../net/{ => intel_wired_lan}/ixgb/ixgb_ethtool.c | 0
> drivers/net/{ => intel_wired_lan}/ixgb/ixgb_hw.c | 0
> drivers/net/{ => intel_wired_lan}/ixgb/ixgb_hw.h | 0
> drivers/net/{ => intel_wired_lan}/ixgb/ixgb_ids.h | 0
> drivers/net/{ => intel_wired_lan}/ixgb/ixgb_main.c | 0
> .../net/{ => intel_wired_lan}/ixgb/ixgb_osdep.h | 0
> .../net/{ => intel_wired_lan}/ixgb/ixgb_param.c | 0
> drivers/net/{ => intel_wired_lan}/ixgbe/Makefile | 0
> drivers/net/{ => intel_wired_lan}/ixgbe/ixgbe.h | 0
> .../net/{ => intel_wired_lan}/ixgbe/ixgbe_82598.c | 0
> .../net/{ => intel_wired_lan}/ixgbe/ixgbe_82599.c | 0
> .../net/{ => intel_wired_lan}/ixgbe/ixgbe_common.c | 0
> .../net/{ => intel_wired_lan}/ixgbe/ixgbe_common.h | 0
> .../net/{ => intel_wired_lan}/ixgbe/ixgbe_dcb.c | 0
> .../net/{ => intel_wired_lan}/ixgbe/ixgbe_dcb.h | 0
> .../{ => intel_wired_lan}/ixgbe/ixgbe_dcb_82598.c | 0
> .../{ => intel_wired_lan}/ixgbe/ixgbe_dcb_82598.h | 0
> .../{ => intel_wired_lan}/ixgbe/ixgbe_dcb_82599.c | 0
> .../{ => intel_wired_lan}/ixgbe/ixgbe_dcb_82599.h | 0
> .../net/{ => intel_wired_lan}/ixgbe/ixgbe_dcb_nl.c | 0
> .../{ => intel_wired_lan}/ixgbe/ixgbe_ethtool.c | 0
> .../net/{ => intel_wired_lan}/ixgbe/ixgbe_fcoe.c | 0
> .../net/{ => intel_wired_lan}/ixgbe/ixgbe_fcoe.h | 0
> .../net/{ => intel_wired_lan}/ixgbe/ixgbe_main.c | 0
> .../net/{ => intel_wired_lan}/ixgbe/ixgbe_mbx.c | 0
> .../net/{ => intel_wired_lan}/ixgbe/ixgbe_mbx.h | 0
> .../net/{ => intel_wired_lan}/ixgbe/ixgbe_phy.c | 0
> .../net/{ => intel_wired_lan}/ixgbe/ixgbe_phy.h | 0
> .../net/{ => intel_wired_lan}/ixgbe/ixgbe_sriov.c | 0
> .../net/{ => intel_wired_lan}/ixgbe/ixgbe_sriov.h | 0
> .../net/{ => intel_wired_lan}/ixgbe/ixgbe_type.h | 0
> drivers/net/{ => intel_wired_lan}/ixgbevf/Makefile | 0
> .../net/{ => intel_wired_lan}/ixgbevf/defines.h | 0
> .../net/{ => intel_wired_lan}/ixgbevf/ethtool.c | 0
> .../net/{ => intel_wired_lan}/ixgbevf/ixgbevf.h | 0
> .../{ => intel_wired_lan}/ixgbevf/ixgbevf_main.c | 0
> drivers/net/{ => intel_wired_lan}/ixgbevf/mbx.c | 0
> drivers/net/{ => intel_wired_lan}/ixgbevf/mbx.h | 0
> drivers/net/{ => intel_wired_lan}/ixgbevf/regs.h | 0
> drivers/net/{ => intel_wired_lan}/ixgbevf/vf.c | 0
> drivers/net/{ => intel_wired_lan}/ixgbevf/vf.h | 0
> 107 files changed, 224 insertions(+), 233 deletions(-)
>
NAK
I agree with Stephen that this will generate a lot of confusion and....
First, I think we need to keep the documentation in /Documentation/networking.
Second, the changes are extensive and would create a lot of regression testing.
We have been looking at solutions like this for future
drivers/hardware and is on the list of items we are currently working
on, but feel it should not be made retroactively due to the regression
testing and massive changes that would need to be made.
--
Cheers,
Jeff
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
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-10-11 23:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-10 20:42 [RFC PATCH net-next] drivers/net Documentation/networking: Create directory intel_wired_lan Joe Perches
2010-10-10 21:44 ` Stephen Hemminger
2010-10-11 0:41 ` Joe Perches
2010-10-11 23:52 ` Jeff Kirsher [this message]
2010-10-12 0:00 ` Joe Perches
2010-10-13 22:28 ` Joe Perches
2010-10-14 4:57 ` Jeff Kirsher
2010-10-14 5:57 ` Joe Perches
2010-10-14 9:34 ` Jeff Kirsher
2010-10-14 19:30 ` Joe Perches
2010-10-14 21:37 ` Michal Marek
2010-10-14 22:20 ` 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='AANLkTikVKufQRuMGd=cdig7ff4k2aw9Q1FWwMz3pgon-@mail.gmail.com' \
--to=jeffrey.t.kirsher@intel.com \
--cc=bruce.w.allan@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=gregory.v.rose@intel.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).