Re: [RFC net-next 0/2] Create ancient subdirectories for old hardware

2016-03-19 Thread Joe Perches
On Fri, 2016-03-18 at 23:16 -0400, David Miller wrote: > From: Joe Perches  Date: Fri, 18 Mar 2016 19:28:02 -0700 > > On Fri, 2016-03-18 at 22:11 -0400, David Miller wrote: > >> From: Joe Perches Date: Fri, 18 Mar 2016 17:33:29 -0700 > >> > Maybe something like this:  > >> > Old, rare, and unsuppo

Re: [RFC net-next 0/2] Create ancient subdirectories for old hardware

2016-03-18 Thread Joe Perches
On Fri, 2016-03-18 at 22:11 -0400, David Miller wrote: > From: Joe Perches > 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 wi

[RFC net-next 0/2] Create ancient subdirectories for old hardware

2016-03-18 Thread Joe Perches
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. Joe Perches (2): drivers/net: Create an ANCIENT_NETDEVICES symbol chelsio: Move original cxgb driver into ancient

Re: [RFC net-next 0/2] Create ancient subdirectories for old hardware

2016-03-18 Thread David Miller
From: Joe Perches Date: Fri, 18 Mar 2016 19:28:02 -0700 > On Fri, 2016-03-18 at 22:11 -0400, David Miller wrote: >> From: Joe Perches >> Date: Fri, 18 Mar 2016 17:33:29 -0700 >> >> > Maybe something like this: >> >  >> > Old, rare, and unsupported hardware should be exposed as ancient. >> >  >>

Re: [RFC net-next 0/2] Create ancient subdirectories for old hardware

2016-03-18 Thread David Miller
From: Joe Perches 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