From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 00/11] Fix some doc build warnings/errors and broken links
Date: Thu, 10 May 2018 14:22:35 -0600 [thread overview]
Message-ID: <20180510142235.221da447@lwn.net> (raw)
In-Reply-To: <cover.1525870886.git.mchehab+samsung@kernel.org>
On Wed, 9 May 2018 10:18:43 -0300
Mauro Carvalho Chehab <mchehab+samsung@kernel.org> wrote:
> Patches 1 to 5 on this series contain the patches that weren't yet
> applied from the past patch series and touch only at Documentation.
> There are two changes there:
> patch 2: fixed the description and added a c/c to cgroup maintainers;
> patch 4: rewritten according with Louis request, droping several hunks.
Of these, I've applied 2, 4, and 6. The networking and crypto folks like
to apply their own documentation fixes; I assume they'll pick these up.
> Patch 6 rewrites scripts/documentation-file-ref-check on Perl,
> adding an auto-fix feature.
Applied this one.
> Patches 7 and 8 fix things that would cause troubles for the
> automatic autocorrection tool.
#7 is applied. #8 doesn't apply, though; I'm not sure which tree you made
it against? In any case, I've stopped here for now.
> Patch 9 touches a lot of random places (including MAINTAINERS)
> that contain broken links and can be auto-fixed. It could be
> broken into one patch per touched file, but I think that is
> overkill.
Let's keep this one (and the ones that follow) aside. I'm happy to apply
them, but I think they are best applied as an end-of-merge-window thing. I
envision lots of conflicts, and I already have a pile of those to explain
to Linus this time around.
Sound good?
Thanks,
jon
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-05-10 20:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 13:18 [PATCH v2 00/11] Fix some doc build warnings/errors and broken links Mauro Carvalho Chehab
2018-05-09 13:18 ` [PATCH v2 01/11] docs: can.rst: fix a footnote reference Mauro Carvalho Chehab
2018-05-09 13:18 ` [PATCH v2 02/11] docs: admin-guide: add cgroup-v2 documentation Mauro Carvalho Chehab
2018-05-10 18:40 ` Tejun Heo
2018-05-10 20:02 ` Jonathan Corbet
2018-05-09 13:18 ` [PATCH v2 03/11] docs: crypto_engine.rst: Fix two parse warnings Mauro Carvalho Chehab
2018-05-09 13:18 ` [PATCH v2 04/11] docs: dell_rbu.txt: fix location of request_firmware Mauro Carvalho Chehab
2018-05-09 15:06 ` Mauro Carvalho Chehab
2018-05-09 13:18 ` [PATCH v2 05/11] docs: uio-howto.rst: use a code block to solve a warning Mauro Carvalho Chehab
2018-05-09 13:18 ` [PATCH v2 06/11] scripts/documentation-file-ref-check: rewrite it in perl with auto-fix mode Mauro Carvalho Chehab
2018-05-09 13:18 ` [PATCH v2 07/11] docs: ranoops.rst: fix location of ramoops.txt Mauro Carvalho Chehab
2018-05-09 13:18 ` [PATCH v2 08/11] docs: refcount-vs-atomic.rst: prefix url with https Mauro Carvalho Chehab
2018-05-09 13:43 ` Andrea Parri
2018-05-09 14:40 ` Mauro Carvalho Chehab
2018-05-09 13:18 ` [PATCH v2 10/11] arch/*: Kconfig: fix documentation for NMI watchdog Mauro Carvalho Chehab
2018-05-09 13:18 ` [PATCH v2 11/11] docs: fix broken references with multiple hints Mauro Carvalho Chehab
2018-05-09 19:22 ` James Morris
2018-05-15 10:28 ` Bartlomiej Zolnierkiewicz
2018-05-15 14:52 ` Steven Rostedt
2018-05-22 17:31 ` Rob Herring
2018-05-10 20:22 ` Jonathan Corbet [this message]
2018-05-10 21:28 ` [PATCH v2 00/11] Fix some doc build warnings/errors and broken links Mauro Carvalho Chehab
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=20180510142235.221da447@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=mchehab@infradead.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).