From: Christian Brauner <brauner@kernel.org>
To: corbet@lwn.net, Vincenzo Mezzela <vincenzo.mezzela@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
skhan@linuxfoundation.org
Subject: Re: [PATCH] docs: filesystems: fix typo in docs
Date: Fri, 9 Feb 2024 10:38:54 +0100 [thread overview]
Message-ID: <20240209-objekt-wertbrief-78f8e50bc261@brauner> (raw)
In-Reply-To: <20240208162032.109184-1-vincenzo.mezzela@gmail.com>
On Thu, 08 Feb 2024 17:20:32 +0100, Vincenzo Mezzela wrote:
> This patch resolves a spelling error in the filesystem documentation.
>
> It is submitted as part of my application to the "Linux Kernel Bug
> Fixing Spring Unpaid 2024" mentorship program of the Linux Kernel
> Foundation.
>
>
> [...]
Applied to the vfs.misc branch of the vfs/vfs.git tree.
Patches in the vfs.misc branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.misc
[1/1] docs: filesystems: fix typo in docs
https://git.kernel.org/vfs/vfs/c/f1d1f00279f6
prev parent reply other threads:[~2024-02-09 9:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 16:20 [PATCH] docs: filesystems: fix typo in docs Vincenzo Mezzela
2024-02-09 9:38 ` Christian Brauner
2024-02-09 14:21 ` Jonathan Corbet
2024-02-09 9:38 ` Christian Brauner [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=20240209-objekt-wertbrief-78f8e50bc261@brauner \
--to=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=vincenzo.mezzela@gmail.com \
/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