From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
"Stephen Rothwell" <sfr@canb.auug.org.au>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: nios2: add missing ReST file
Date: Mon, 7 Dec 2020 14:00:12 -0700 [thread overview]
Message-ID: <20201207140012.2f4cf4da@lwn.net> (raw)
In-Reply-To: <e51c4692c4420d28bca35f553a9a3f3d78404d99.1607331056.git.mchehab+huawei@kernel.org>
On Mon, 7 Dec 2020 09:56:20 +0100
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:
> changeset ed13a92d0fde ("docs: archis: add a per-architecture features list")
> besides having a typo on its title, it was missing the feature file.
>
> Add it.
>
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Fixes: ed13a92d0fde ("docs: archis: add a per-architecture features list")
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> ---
>
> Jon/Stephen,
>
> I ended forgetting to add this one to the patch I sent. Sorry for that!
>
> If not too late, feel free to fold this patch with the past one.
>
> Documentation/nios2/features.rst | 3 +++
> 1 file changed, 3 insertions(+)
> create mode 100644 Documentation/nios2/features.rst
>
> diff --git a/Documentation/nios2/features.rst b/Documentation/nios2/features.rst
> new file mode 100644
> index 000000000000..8449e63f69b2
> --- /dev/null
> +++ b/Documentation/nios2/features.rst
> @@ -0,0 +1,3 @@
> +.. SPDX-License-Identifier: GPL-2.0
> +
> +.. kernel-feat:: $srctree/Documentation/features nios2
I've applied this, thanks.
jon
prev parent reply other threads:[~2020-12-07 21:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201207185257.1198e407@canb.auug.org.au>
2020-12-07 8:56 ` [PATCH] docs: nios2: add missing ReST file Mauro Carvalho Chehab
2020-12-07 21:00 ` 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=20201207140012.2f4cf4da@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=sfr@canb.auug.org.au \
/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).