From: Joe Perches <joe@perches.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC net-next 0/2] Create ancient subdirectories for old hardware
Date: Fri, 18 Mar 2016 19:28:02 -0700 [thread overview]
Message-ID: <1458354482.26915.35.camel@perches.com> (raw)
In-Reply-To: <20160318.221153.997255526626920777.davem@davemloft.net>
On Fri, 2016-03-18 at 22:11 -0400, David Miller wrote:
> From: Joe Perches <joe@perches.com>
> Date: Fri, 18 Mar 2016 17:33:29 -0700
>
> > Maybe something like this:
> >
> > Old, rare, and unsupported hardware should be exposed as ancient.
> >
> > The drivers for these ancient hardwares are generally untested with
> > current kernels.
>
> Moving drivers has a long term maintainence cost.
>
> If they've moved into drivers/net proper, we have to maintain
> them there forever.
I don't doubt that.
All files are still in drivers/net, just possibly in
separate subdirectories for easier visibility to
determine if changes like what were proposed for cxgb
should actually be done or not.
next prev parent reply other threads:[~2016-03-19 2:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 9:32 [PATCH] net: consolidate lock/unlock into unlock_wait Nicholas Mc Guire
2016-03-18 21:37 ` David Miller
2016-03-18 22:35 ` Joe Perches
2016-03-19 0:33 ` [RFC net-next 0/2] Create ancient subdirectories for old hardware Joe Perches
2016-03-19 0:33 ` [RFC net-next 1/2] drivers/net: Create an ANCIENT_NETDEVICES symbol Joe Perches
2016-03-19 0:33 ` [RFC net-next 2/2] chelsio: Move original cxgb driver into ancient subdirectory Joe Perches
2016-03-19 2:11 ` [RFC net-next 0/2] Create ancient subdirectories for old hardware David Miller
2016-03-19 2:28 ` Joe Perches [this message]
2016-03-19 3:16 ` David Miller
2016-03-19 15:36 ` Joe Perches
2016-03-19 7:24 ` [PATCH] net: consolidate lock/unlock into unlock_wait Nicholas Mc Guire
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=1458354482.26915.35.camel@perches.com \
--to=joe@perches.com \
--cc=davem@davemloft.net \
--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