From: Jonathan Corbet <corbet@lwn.net>
To: Stefan Schmidt <stefan@datenfreihafen.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
linux-doc@vger.kernel.org, linux-wpan@vger.kernel.org
Subject: Re: [PATCH 0/2] doc: net: ieee802154: move from plain text to rst
Date: Wed, 27 Feb 2019 13:18:56 -0700 [thread overview]
Message-ID: <20190227131856.2a9cfdde@lwn.net> (raw)
In-Reply-To: <20190227195914.4594-1-stefan@datenfreihafen.org>
On Wed, 27 Feb 2019 20:59:12 +0100
Stefan Schmidt <stefan@datenfreihafen.org> wrote:
> The patches are based on net-next, but they only touch the networking book so I
> would not expect and trouble. From what I have seen they would go through
> Jonathan's tree after being acked by Dave? If you want this patches against a
> different tree let me know.
Usually Dave takes networking documentation patches directly, so that is
what I would expect here.
I took a quick look anyway; seems generally good. The main comment I
would make is that much of what's there would be better placed as
kerneldoc comments in the code itself that can then be pulled into the
formatted docs. But that can be a job for another day...
Thanks,
jon
next prev parent reply other threads:[~2019-02-27 20:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 19:59 [PATCH 0/2] doc: net: ieee802154: move from plain text to rst Stefan Schmidt
2019-02-27 19:59 ` [PATCH 1/2] doc: net: ieee802154: introduce IEEE 802.15.4 subsystem doc in rst style Stefan Schmidt
2019-02-27 21:51 ` Randy Dunlap
2019-02-27 19:59 ` [PATCH 2/2] doc: net: ieee802154: remove old plain text docs after switching to rst Stefan Schmidt
2019-02-27 20:18 ` Jonathan Corbet [this message]
2019-02-27 21:20 ` [PATCH 0/2] doc: net: ieee802154: move from plain text " Stefan Schmidt
2019-03-02 1:01 ` David Miller
2019-03-02 1:03 ` David Miller
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=20190227131856.2a9cfdde@lwn.net \
--to=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stefan@datenfreihafen.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;
as well as URLs for NNTP newsgroup(s).