From: Jonathan Corbet <corbet@lwn.net>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Amir Levy <amir.jer.levy@intel.com>,
andreas.noever@gmail.com, bhelgaas@google.com,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
mario_limonciello@dell.com, thunderbolt-linux@intel.com,
mika.westerberg@intel.com, tomas.winkler@intel.com,
xiong.y.zhang@intel.com
Subject: Re: [PATCH v9 7/8] thunderbolt: Networking doc
Date: Thu, 10 Nov 2016 07:24:22 -0700 [thread overview]
Message-ID: <20161110072422.484c89ad@lwn.net> (raw)
In-Reply-To: <20161109160002.GA9111@kroah.com>
On Wed, 9 Nov 2016 17:00:02 +0100
Greg KH <gregkh@linuxfoundation.org> wrote:
> > Documentation/00-INDEX | 2 +
> > Documentation/thunderbolt/networking.txt | 132 +++++++++++++++++++++++++++++++
>
> Note, new files should be in .rst format, and live in the new
> subdirectory for them (somewhere in Documentation, don't know off the
> top of my head...)
This one's almost in RST already, happily.
We haven't really figured out a hierarchy for device-specific docs like
this yet; I should get on that, I guess.
I do believe that we should separate documents for end users from those
aimed at kernel developers; those are two very different audiences
looking for different kinds of information.
Thanks,
jon
next prev parent reply other threads:[~2016-11-10 14:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 14:20 [PATCH v9 0/8] thunderbolt: Introducing Thunderbolt(TM) Networking Amir Levy
2016-11-09 14:20 ` [PATCH v9 1/8] thunderbolt: Macro rename Amir Levy
2016-11-09 14:20 ` [PATCH v9 2/8] thunderbolt: Updating the register definitions Amir Levy
2016-11-09 14:20 ` [PATCH v9 3/8] thunderbolt: Communication with the ICM (firmware) Amir Levy
2016-11-09 14:20 ` [PATCH v9 4/8] thunderbolt: Networking state machine Amir Levy
2016-11-09 14:20 ` [PATCH v9 5/8] thunderbolt: Networking transmit and receive Amir Levy
2016-11-09 14:20 ` [PATCH v9 6/8] thunderbolt: Kconfig for Thunderbolt Networking Amir Levy
2016-11-09 14:20 ` [PATCH v9 7/8] thunderbolt: Networking doc Amir Levy
2016-11-09 16:00 ` Greg KH
2016-11-10 11:47 ` Levy, Amir (Jer)
2016-11-10 11:53 ` Greg KH
2016-11-10 14:24 ` Jonathan Corbet [this message]
2016-11-09 14:20 ` [PATCH v9 8/8] thunderbolt: Adding maintainer entry Amir Levy
2016-11-09 14:36 ` [PATCH v9 0/8] thunderbolt: Introducing Thunderbolt(TM) Networking Simon Guinot
2016-11-09 15:42 ` Levy, Amir (Jer)
2016-11-15 10:59 ` Simon Guinot
2016-11-18 8:48 ` Levy, Amir (Jer)
2016-11-18 10:07 ` gregkh
2016-11-20 6:30 ` Levy, Amir (Jer)
2016-11-21 12:22 ` gregkh
2016-11-18 11:20 ` Simon Guinot
2016-11-22 17:28 ` Simon Guinot
2016-11-22 17:36 ` Mario.Limonciello
2016-11-24 20:35 ` Levy, Amir (Jer)
2016-11-09 16:02 ` Greg KH
2016-11-10 11:39 ` Levy, Amir (Jer)
2016-11-10 11:44 ` Greg KH
2016-11-10 11:48 ` Levy, Amir (Jer)
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=20161110072422.484c89ad@lwn.net \
--to=corbet@lwn.net \
--cc=amir.jer.levy@intel.com \
--cc=andreas.noever@gmail.com \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mario_limonciello@dell.com \
--cc=mika.westerberg@intel.com \
--cc=netdev@vger.kernel.org \
--cc=thunderbolt-linux@intel.com \
--cc=tomas.winkler@intel.com \
--cc=xiong.y.zhang@intel.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).