devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Rob Herring <robh+dt@kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Andy Whitcroft <apw@canonical.com>,
	Dwaipayan Ray <dwaipayanray1@gmail.com>,
	Joe Perches <joe@perches.com>,
	Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	devicetree@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 29/32] docs: dt: update writing-schema.rst references
Date: Wed, 7 Apr 2021 10:06:27 +0200	[thread overview]
Message-ID: <20210407100627.13071b72@coco.lan> (raw)
In-Reply-To: <CAL_Jsq+3kqzQi+7emMWkuhyh2aj8qLy6nLS--J2P57Bw_jOCvw@mail.gmail.com>

Em Tue, 6 Apr 2021 10:04:57 -0500
Rob Herring <robh+dt@kernel.org> escreveu:

> On Thu, Apr 1, 2021 at 7:17 AM Mauro Carvalho Chehab
> <mchehab+huawei@kernel.org> wrote:
> >
> > Changeset b83db5b84900 ("docs: dt: Group DT docs into relevant sub-sections")
> > renamed: Documentation/devicetree/writing-schema.rst
> > to: Documentation/devicetree/bindings/writing-schema.rst.
> >
> > Update the cross-references accordingly.
> >
> > Fixes: b83db5b84900 ("docs: dt: Group DT docs into relevant sub-sections")
> > Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> > ---
> >  Documentation/devicetree/bindings/submitting-patches.rst | 2 +-
> >  scripts/checkpatch.pl                                    | 2 +-
> >  2 files changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/submitting-patches.rst b/Documentation/devicetree/bindings/submitting-patches.rst
> > index ee4feb53f8d0..104fa8fb2c17 100644
> > --- a/Documentation/devicetree/bindings/submitting-patches.rst
> > +++ b/Documentation/devicetree/bindings/submitting-patches.rst
> > @@ -25,7 +25,7 @@ I. For patch submitters
> >
> >         make dt_binding_check
> >
> > -     See Documentation/devicetree/writing-schema.rst for more details about
> > +     See Documentation/devicetree/bindings/writing-schema.rst for more details about  
> 
> We should make this a rSt link instead.

It shouldn't be needed, as Documentation/sphinx/automarkup.py has a rule
which converts Documentation/* into a cross reference using this
regex:

	RE_doc = re.compile(r'(\bDocumentation/)?((\.\./)*[\w\-/]+)\.(rst|txt)')


Thanks,
Mauro

  reply	other threads:[~2021-04-07  8:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-01 12:17 [PATCH 00/32] Fix broken documentation file references Mauro Carvalho Chehab
2021-04-01 12:17 ` [PATCH 26/32] dt-bindings: iommu: mediatek: update mediatek,iommu.yaml references Mauro Carvalho Chehab
2021-04-01 12:17 ` [PATCH 27/32] dt-bindings: i3c: update i3c.yaml references Mauro Carvalho Chehab
2021-04-06 15:05   ` Rob Herring
2021-04-01 12:17 ` [PATCH 29/32] docs: dt: update writing-schema.rst references Mauro Carvalho Chehab
2021-04-06 15:04   ` Rob Herring
2021-04-07  8:06     ` Mauro Carvalho Chehab [this message]
2021-04-07 14:45   ` Rob Herring

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=20210407100627.13071b72@coco.lan \
    --to=mchehab+huawei@kernel.org \
    --cc=apw@canonical.com \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=dwaipayanray1@gmail.com \
    --cc=joe@perches.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=robh+dt@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).