From: Jonathan Corbet <corbet@lwn.net>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: [PATCH] docs: dt: submitting-patches: Fix grammar in subsystem section
Date: Mon, 15 Mar 2021 13:26:40 -0600 [thread overview]
Message-ID: <87wnu81amn.fsf@meer.lwn.net> (raw)
In-Reply-To: <20210309130650.2318419-1-geert+renesas@glider.be>
Geert Uytterhoeven <geert+renesas@glider.be> writes:
> Reword the subsystem bindings section to make sense, from a grammatical
> point of view.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> Documentation/devicetree/bindings/submitting-patches.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/submitting-patches.rst b/Documentation/devicetree/bindings/submitting-patches.rst
> index 68129ff09967d5d7..1d11c25249ff5465 100644
> --- a/Documentation/devicetree/bindings/submitting-patches.rst
> +++ b/Documentation/devicetree/bindings/submitting-patches.rst
> @@ -75,8 +75,8 @@ II. For kernel maintainers
> binding, and it hasn't received an Acked-by from the devicetree
> maintainers after a few weeks, go ahead and take it.
>
> - Subsystem bindings (anything affecting more than a single device)
> - then getting a devicetree maintainer to review it is required.
> + For subsystem bindings (anything affecting more than a single device),
> + getting a devicetree maintainer to review it is required.
Applied, thanks.
jon
prev parent reply other threads:[~2021-03-15 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 13:06 [PATCH] docs: dt: submitting-patches: Fix grammar in subsystem section Geert Uytterhoeven
2021-03-09 17:16 ` Randy Dunlap
2021-03-15 19:26 ` 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=87wnu81amn.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--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).