From: "Tobin C. Harding" <me@tobin.cc>
To: Jonathan Corbet <corbet@lwn.net>
Cc: "Tobin C. Harding" <me@tobin.cc>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
"David S. Miller" <davem@davemloft.net>,
linux-doc@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] docs: e100[0] fix build errors
Date: Fri, 22 Jun 2018 10:37:04 +1000 [thread overview]
Message-ID: <20180622003708.31848-1-me@tobin.cc> (raw)
Hi Jonathan,
I may be a little confused here, I'm getting docs build failure on
Linus' mainline, linux-next, and your docs-next but different errors.
There seems to be patches to the first two trees that are not in your
docs-next tree?
Do networking docs typically go through your tree? Looks like
networking has done some conversion to rst that hasn't gone through your
tree. Or else my git skills are failing.
This patch set fixes current docs build failure on Linus' mainline
commit: (ba4dbdedd3ed Merge tag 'jfs-4.18' of git://github.com/kleikamp/linux-shaggy)
(FYI this is 8 commits after Linux 4.18-rc1).
And also same build errors on today's linux-next
8439c34f07a3 (tag: next-20180621, linux-next/master, linux-next) Add linux-next specific files for 20180621
I pulled your tree, just to make sure I'm pulling the correct one I got
a49d9c0ae46e (HEAD -> docs-next, tag: docs-4.18, corbet/docs-next) Documentation: document hung_task_panic kernel parameter
I split the patches in between the two drivers to enable use of the
'Fixes:' tag.
One question, is there are standard spacing after headings. I attempted
to maintain uniformity within each file but this has resulted in the two
files being different. One has no space after section headings
section heading
---------------
Some text with no newline.
While the other file uses a single newline after section headings.
While on the topic of newlines and headings; is there a correct number
of newlines to have _before_ a heading?
I did not find this information when looking at
Documentation/doc-guide/sphinx.rst
If there is a ruling on these newlines I can re-spin this set with an
added patch to fix all the newlines in both e1000.rst and e100.rst
thanks,
Tobin.
Tobin C. Harding (4):
Documentation: e100: Use correct heading adornment
Documentation: e1000: Use correct heading adornment
Documentation: e100: Fix docs build error
Documentation: e1000: Fix docs build error
Documentation/networking/e100.rst | 112 +++++++++++++++--------------
Documentation/networking/e1000.rst | 76 ++++++++++----------
2 files changed, 96 insertions(+), 92 deletions(-)
--
2.17.1
next reply other threads:[~2018-06-22 0:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 0:37 Tobin C. Harding [this message]
2018-06-22 0:37 ` [PATCH 1/4] Documentation: e100: Use correct heading adornment Tobin C. Harding
2018-06-22 16:44 ` Jeff Kirsher
2018-06-22 0:37 ` [PATCH 2/4] Documentation: e1000: " Tobin C. Harding
2018-06-22 16:45 ` Jeff Kirsher
2018-06-22 0:37 ` [PATCH 3/4] Documentation: e100: Fix docs build error Tobin C. Harding
2018-06-22 16:46 ` Jeff Kirsher
2018-06-22 0:37 ` [PATCH 4/4] Documentation: e1000: " Tobin C. Harding
2018-06-22 16:47 ` Jeff Kirsher
2018-06-22 16:44 ` [PATCH 0/4] docs: e100[0] fix build errors Jeff Kirsher
2018-06-23 1:38 ` David Miller
2018-06-22 20:22 ` Randy Dunlap
2018-06-24 23:41 ` Tobin C. Harding
2018-06-25 1:11 ` Kirsher, Jeffrey T
2018-06-25 2: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=20180622003708.31848-1-me@tobin.cc \
--to=me@tobin.cc \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=jeffrey.t.kirsher@intel.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
all inboxes | Powered by JetHome®