From: Jonathan Corbet <corbet@lwn.net>
To: Askar Safin <safinaskar@gmail.com>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: patches@lists.linux.dev, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] doc: early_userspace_support.rst: trivial fix: directory -> file
Date: Mon, 23 Feb 2026 14:53:42 -0700 [thread overview]
Message-ID: <871pib3z4p.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260220165238.4162735-1-safinaskar@gmail.com>
Askar Safin <safinaskar@gmail.com> writes:
> Trivial fix.
>
> Signed-off-by: Askar Safin <safinaskar@gmail.com>
> ---
> .../driver-api/early-userspace/early_userspace_support.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/driver-api/early-userspace/early_userspace_support.rst b/Documentation/driver-api/early-userspace/early_userspace_support.rst
> index 61bdeac1b..60d1e1bc9 100644
> --- a/Documentation/driver-api/early-userspace/early_userspace_support.rst
> +++ b/Documentation/driver-api/early-userspace/early_userspace_support.rst
> @@ -73,7 +73,7 @@ usr/gen_initramfs.sh. This means that CONFIG_INITRAMFS_SOURCE
> can really be interpreted as any legal argument to
> gen_initramfs.sh. If a directory is specified as an argument then
> the contents are scanned, uid/gid translation is performed, and
> -usr/gen_init_cpio file directives are output. If a directory is
> +usr/gen_init_cpio file directives are output. If a file is
> specified as an argument to usr/gen_initramfs.sh then the
"Trivial fix" is not a great changelog ... but I've applied the patch,
thanks.
jon
prev parent reply other threads:[~2026-02-23 21:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 16:52 [PATCH] doc: early_userspace_support.rst: trivial fix: directory -> file Askar Safin
2026-02-23 21:53 ` 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=871pib3z4p.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@lists.linux.dev \
--cc=safinaskar@gmail.com \
--cc=skhan@linuxfoundation.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