From: Stephen Hemminger <stephen@networkplumber.org>
To: "Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"klassert@kernel.org" <klassert@kernel.org>,
"akiyano@amazon.com" <akiyano@amazon.com>,
"irusskikh@marvell.com" <irusskikh@marvell.com>,
"ioana.ciornei@nxp.com" <ioana.ciornei@nxp.com>,
"kys@microsoft.com" <kys@microsoft.com>,
"saeedm@mellanox.com" <saeedm@mellanox.com>,
"jdmason@kudzu.us" <jdmason@kudzu.us>,
"snelson@pensando.io" <snelson@pensando.io>,
"GR-Linux-NIC-Dev@marvell.com" <GR-Linux-NIC-Dev@marvell.com>,
"stuyoder@gmail.com" <stuyoder@gmail.com>,
"sgoutham@marvell.com" <sgoutham@marvell.com>,
"luobin9@huawei.com" <luobin9@huawei.com>,
"csully@google.com" <csully@google.com>,
"kou.ishizaki@toshiba.co.jp" <kou.ishizaki@toshiba.co.jp>,
"peppe.cavallaro@st.com" <peppe.cavallaro@st.com>,
"chessman@tux.org" <chessman@tux.org>
Subject: Re: [RFC 1/8] docs: networking: reorganize driver documentation again
Date: Thu, 11 Jun 2020 15:18:42 -0700 [thread overview]
Message-ID: <20200611151842.392642c5@hermes.lan> (raw)
In-Reply-To: <61CC2BC414934749BD9F5BF3D5D94044986F4FAE@ORSMSX112.amr.corp.intel.com>
On Thu, 11 Jun 2020 21:17:49 +0000
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com> wrote:
> > -----Original Message-----
> > From: Jakub Kicinski <kuba@kernel.org>
> > Sent: Thursday, June 11, 2020 10:30
> > To: davem@davemloft.net
> > Cc: netdev@vger.kernel.org; linux-doc@vger.kernel.org; Jakub Kicinski
> > <kuba@kernel.org>; klassert@kernel.org; akiyano@amazon.com;
> > irusskikh@marvell.com; ioana.ciornei@nxp.com; kys@microsoft.com;
> > saeedm@mellanox.com; jdmason@kudzu.us; snelson@pensando.io; GR-Linux-
> > NIC-Dev@marvell.com; stuyoder@gmail.com; Kirsher, Jeffrey T
> > <jeffrey.t.kirsher@intel.com>; sgoutham@marvell.com; luobin9@huawei.com;
> > csully@google.com; kou.ishizaki@toshiba.co.jp; peppe.cavallaro@st.com;
> > chessman@tux.org
> > 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@kernel.org>
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.
next prev parent reply other threads:[~2020-06-11 22:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 17:30 [RFC 0/8] net: organize driver docs by device type Jakub Kicinski
2020-06-11 17:30 ` [RFC 1/8] docs: networking: reorganize driver documentation again Jakub Kicinski
2020-06-11 21:17 ` Kirsher, Jeffrey T
2020-06-11 21:49 ` Jakub Kicinski
2020-06-11 22:18 ` Stephen Hemminger [this message]
2020-06-11 23:09 ` Jakub Kicinski
2020-06-11 23:43 ` Kirsher, Jeffrey T
2020-06-12 23:56 ` Shannon Nelson
2020-06-11 17:30 ` [RFC 2/8] docs: networking: move z8530 to the hw driver section Jakub Kicinski
2020-06-11 17:30 ` [RFC 3/8] docs: networking: move baycom " Jakub Kicinski
2020-06-11 17:30 ` [RFC 4/8] docs: networking: move ray_cs " Jakub Kicinski
2020-06-11 17:30 ` [RFC 5/8] docs: networking: move remaining Ethernet driver docs to the hw section Jakub Kicinski
2020-06-11 17:30 ` [RFC 6/8] docs: networking: move AppleTalk / LocalTalk drivers to the hw driver section Jakub Kicinski
2020-06-11 17:30 ` [RFC 7/8] docs: networking: move ATM " Jakub Kicinski
2020-06-11 17:30 ` [RFC 8/8] docs: networking: move FDDI " Jakub Kicinski
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=20200611151842.392642c5@hermes.lan \
--to=stephen@networkplumber.org \
--cc=GR-Linux-NIC-Dev@marvell.com \
--cc=akiyano@amazon.com \
--cc=chessman@tux.org \
--cc=csully@google.com \
--cc=davem@davemloft.net \
--cc=ioana.ciornei@nxp.com \
--cc=irusskikh@marvell.com \
--cc=jdmason@kudzu.us \
--cc=jeffrey.t.kirsher@intel.com \
--cc=klassert@kernel.org \
--cc=kou.ishizaki@toshiba.co.jp \
--cc=kuba@kernel.org \
--cc=kys@microsoft.com \
--cc=linux-doc@vger.kernel.org \
--cc=luobin9@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=saeedm@mellanox.com \
--cc=sgoutham@marvell.com \
--cc=snelson@pensando.io \
--cc=stuyoder@gmail.com \
/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).