From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] Some cross-reference fixes due to fixes renames
Date: Tue, 25 Feb 2020 03:05:01 -0700 [thread overview]
Message-ID: <20200225030501.48770bc2@lwn.net> (raw)
In-Reply-To: <cover.1582361737.git.mchehab+huawei@kernel.org>
On Sat, 22 Feb 2020 10:00:00 +0100
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:
> There are some references that got broken due to renames
> (mostly .txt to .yaml and .rst, but also some files got moved
> to other directories).
>
> The first patch actually contains a fix for
> documentation-file-ref-check, with currently reports several
> false positives.
>
> Mauro Carvalho Chehab (7):
> scripts: documentation-file-ref-check: improve :doc: handling
> docs: dt: fix several broken references due to renames
> docs: fix broken references to text files
> docs: adm1177: fix a broken reference
> docs: fix broken references for ReST files that moved around
> docs: remove nompx kernel parameter and intel_mpx from index.rst
> docs: gpu: i915.rst: fix warnings due to file renames
OK, I've applied the first and the last of those. Patches 2 and 4 have
already been applied elsewhere. Parts 3 and 5 have horrific conflicts
against docs-next, so I've passed them by. That leaves nompx, which had
a comment from Dave Hansen.
Thanks,
jon
prev parent reply other threads:[~2020-02-25 10:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-22 9:00 [PATCH 0/7] Some cross-reference fixes due to fixes renames Mauro Carvalho Chehab
2020-02-22 9:00 ` [PATCH 1/7] scripts: documentation-file-ref-check: improve :doc: handling Mauro Carvalho Chehab
2020-02-22 9:00 ` [PATCH 2/7] docs: dt: fix several broken references due to renames Mauro Carvalho Chehab
2020-02-24 0:07 ` Andrew Jeffery
2020-02-24 13:02 ` Dan Murphy
2020-02-24 14:55 ` Amit Kucheria
2020-02-24 18:14 ` Rob Herring
2020-02-27 9:16 ` Daniel Lezcano
2020-02-22 9:00 ` [PATCH 3/7] docs: fix broken references to text files Mauro Carvalho Chehab
2020-02-22 17:51 ` Daniel Vetter
2020-02-24 9:26 ` Federico Vaga
2020-03-25 2:42 ` Stephen Boyd
2020-02-22 9:00 ` [PATCH 4/7] docs: adm1177: fix a broken reference Mauro Carvalho Chehab
2020-02-22 15:48 ` Guenter Roeck
2020-02-22 9:00 ` [PATCH 5/7] docs: fix broken references for ReST files that moved around Mauro Carvalho Chehab
2020-02-23 8:12 ` Paolo Bonzini
2020-02-22 9:00 ` [PATCH 6/7] docs: remove nompx kernel parameter and intel_mpx from index.rst Mauro Carvalho Chehab
2020-02-24 17:30 ` Dave Hansen
2020-02-25 10:06 ` Jonathan Corbet
2020-02-22 9:00 ` [PATCH 7/7] docs: gpu: i915.rst: fix warnings due to file renames Mauro Carvalho Chehab
2020-02-25 23:36 ` Rodrigo Vivi
2020-02-25 10:05 ` Jonathan Corbet [this message]
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=20200225030501.48770bc2@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@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).