On Thu, 11 Jun 2020 21:17:49 +0000 "Kirsher, Jeffrey T" <jeffrey.t.kirsher@xxxxxxxxx> wrote: > > -----Original Message----- > > From: Jakub Kicinski <kuba@xxxxxxxxxx> > > Sent: Thursday, June 11, 2020 10:30 > > To: davem@xxxxxxxxxxxxx > > Cc: netdev@xxxxxxxxxxxxxxx; linux-doc@xxxxxxxxxxxxxxx; Jakub Kicinski > > <kuba@xxxxxxxxxx>; klassert@xxxxxxxxxx; akiyano@xxxxxxxxxx; > > irusskikh@xxxxxxxxxxx; ioana.ciornei@xxxxxxx; kys@xxxxxxxxxxxxx; > > saeedm@xxxxxxxxxxxx; jdmason@xxxxxxxx; snelson@xxxxxxxxxxx; GR-Linux- > > NIC-Dev@xxxxxxxxxxx; stuyoder@xxxxxxxxx; Kirsher, Jeffrey T > > <jeffrey.t.kirsher@xxxxxxxxx>; sgoutham@xxxxxxxxxxx; luobin9@xxxxxxxxxx; > > csully@xxxxxxxxxx; kou.ishizaki@xxxxxxxxxxxxx; peppe.cavallaro@xxxxxx; > > chessman@xxxxxxx > > Subject: [RFC 1/8] docs: networking: reorganize driver documentation again > > > > Organize driver documentation by device type. Most documents > > have fairly verbose yet uninformative names, so let users > > first select a well defined device type, and then search for > > a particular driver. > > > > While at it rename the section from Vendor drivers to > > Hardware drivers. This seems more accurate, besides people > > sometimes refer to out-of-tree drivers as vendor drivers. > > > > Signed-off-by: Jakub Kicinski <kuba@xxxxxxxxxx> How much of it is still relevant and useful? The last time I checked, lots of this had bad advice about settings. And there was lots of drivers documenting what was generic Linux functionality And still there were references to old commands like ifconfig or ifenslave.
