From: "Tobin C. Harding" <me@tobin.cc>
To: "David S. Miller" <davem@davemloft.net>
Cc: "Tobin C. Harding" <me@tobin.cc>,
Jonathan Corbet <corbet@lwn.net>,
Edward Cree <ecree@solarflare.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
linux-doc@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 net-next 0/3] docs: net: Convert netdev-FAQ to RST
Date: Thu, 26 Jul 2018 15:00:28 +1000 [thread overview]
Message-ID: <20180726050031.1697-1-me@tobin.cc> (raw)
Hi Dave,
Jon answered all the tree questions on v1 so if you will please take
this through your tree that would be awesome.
v2:
- Fix typo 'canonical_path_format' (thanks Edward)
- Add patch fixing references netdev-FAQ
thanks,
Tobin.
Tobin C. Harding (3):
docs: Add rest label the_canonical_patch_format
docs: net: Convert netdev-FAQ to restructured text
docs: Update references to netdev-FAQ
Documentation/bpf/bpf_devel_QA.rst | 21 +-
Documentation/networking/00-INDEX | 2 -
Documentation/networking/index.rst | 1 +
Documentation/networking/netdev-FAQ.rst | 259 ++++++++++++++++++
Documentation/networking/netdev-FAQ.txt | 244 -----------------
Documentation/process/stable-kernel-rules.rst | 2 +-
Documentation/process/submitting-patches.rst | 1 +
7 files changed, 271 insertions(+), 259 deletions(-)
create mode 100644 Documentation/networking/netdev-FAQ.rst
delete mode 100644 Documentation/networking/netdev-FAQ.txt
--
2.17.1
next reply other threads:[~2018-07-26 5:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 5:00 Tobin C. Harding [this message]
2018-07-27 4:28 ` [PATCH v2 net-next 0/3] docs: net: Convert netdev-FAQ to RST David Miller
-- strict thread matches above, loose matches on Subject: below --
2018-07-26 5:02 Tobin C. Harding
2018-07-26 5:06 ` Tobin C. Harding
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=20180726050031.1697-1-me@tobin.cc \
--to=me@tobin.cc \
--cc=ast@kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=ecree@solarflare.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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).