From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Rob Herring <robh+dt@kernel.org>
Cc: "Jonathan Corbet" <corbet@lwn.net>,
"Linux Doc Mailing List" <linux-doc@vger.kernel.org>,
"Nícolas F. R. A. Prado" <nfraprado@protonmail.com>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
devicetree@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 11/29] docs: devicetree: bindings: submitting-patches.rst: avoid using ReST :doc:`foo` markup
Date: Thu, 17 Jun 2021 08:38:15 +0200 [thread overview]
Message-ID: <20210617083815.3a588868@coco.lan> (raw)
In-Reply-To: <CAL_JsqLtZhox5-d81FnWywqM6waBv5fJ26z2n9rMw8wrn4aDqg@mail.gmail.com>
Em Wed, 16 Jun 2021 16:08:05 -0600
Rob Herring <robh+dt@kernel.org> escreveu:
> On Wed, Jun 16, 2021 at 12:27 AM Mauro Carvalho Chehab
> <mchehab+huawei@kernel.org> wrote:
> >
> > The :doc:`foo` tag is auto-generated via automarkup.py.
> > So, use the filename at the sources, instead of :doc:`foo`.
> >
> > Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> > ---
> > .../devicetree/bindings/submitting-patches.rst | 11 ++++++-----
> > 1 file changed, 6 insertions(+), 5 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/submitting-patches.rst b/Documentation/devicetree/bindings/submitting-patches.rst
> > index 104fa8fb2c17..8087780f1685 100644
> > --- a/Documentation/devicetree/bindings/submitting-patches.rst
> > +++ b/Documentation/devicetree/bindings/submitting-patches.rst
> > @@ -7,8 +7,8 @@ Submitting Devicetree (DT) binding patches
> > I. For patch submitters
> > =======================
> >
> > - 0) Normal patch submission rules from Documentation/process/submitting-patches.rst
> > - applies.
> > + 0) Normal patch submission rules from
> > + Documentation/process/submitting-patches.rst applies.
> >
> > 1) The Documentation/ and include/dt-bindings/ portion of the patch should
> > be a separate patch. The preferred subject prefix for binding patches is::
> > @@ -25,8 +25,8 @@ I. For patch submitters
> >
> > make dt_binding_check
> >
> > - See Documentation/devicetree/bindings/writing-schema.rst for more details about
> > - schema and tools setup.
> > + See Documentation/devicetree/bindings/writing-schema.rst for more details
> > + about schema and tools setup.
>
> These don't match $subject.
Well, I just seek for all places where Documentation/* are, and adjusted
them to 80-columns. I'll add a comment.
>
> >
> > 3) DT binding files should be dual licensed. The preferred license tag is
> > (GPL-2.0-only OR BSD-2-Clause).
> > @@ -84,7 +84,8 @@ II. For kernel maintainers
> > III. Notes
> > ==========
> >
> > - 0) Please see :doc:`ABI` for details regarding devicetree ABI.
> > + 0) Please see Documentation/devicetree/bindings/ABI.rst for details
> > + regarding devicetree ABI.
>
> Is this new? You did review my oneliner adding ':doc:' not too long ago.
Yes. It is due to some discussion we had upstream:
https://lore.kernel.org/linux-doc/871r9k6rmy.fsf@meer.lwn.net/
While the html/latex/pdf output is identical (as automarkup.py will
convert Documentation/foo.rst into a cross-reference), using full path
names allow developers to jump directly to other documents when they
have the path name.
>
> >
> > 1) This document is intended as a general familiarization with the process as
> > decided at the 2013 Kernel Summit. When in doubt, the current word of the
> > --
> > 2.31.1
> >
Thanks,
Mauro
next prev parent reply other threads:[~2021-06-17 6:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 6:27 [PATCH v2 00/29] docs: avoid using ReST :doc:`foo` tag Mauro Carvalho Chehab
2021-06-16 6:27 ` [PATCH v2 11/29] docs: devicetree: bindings: submitting-patches.rst: avoid using ReST :doc:`foo` markup Mauro Carvalho Chehab
2021-06-16 22:08 ` Rob Herring
2021-06-17 6:38 ` Mauro Carvalho Chehab [this message]
2021-06-17 19:34 ` [PATCH v2 00/29] docs: avoid using ReST :doc:`foo` tag Jonathan Corbet
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=20210617083815.3a588868@coco.lan \
--to=mchehab+huawei@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfraprado@protonmail.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).