From: "Darrick J. Wong" <djwong@kernel.org>
To: Christian Brauner <brauner@kernel.org>
Cc: Dennis Lam <dennis.lamerice@gmail.com>,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
corbet@lwn.net
Subject: Re: [PATCH] docs:filesystems: fix spelling and grammar mistakes in iomap design page
Date: Tue, 17 Sep 2024 09:17:49 -0700 [thread overview]
Message-ID: <20240917161749.GD182218@frogsfrogsfrogs> (raw)
In-Reply-To: <20240909-frosch-klumpen-dbaee12c22d6@brauner>
On Mon, Sep 09, 2024 at 09:53:28AM +0200, Christian Brauner wrote:
> On Sun, 08 Sep 2024 13:28:42 -0400, Dennis Lam wrote:
> >
>
>
> Applied to the vfs.blocksize branch of the vfs/vfs.git tree.
> Patches in the vfs.blocksize branch should appear in linux-next soon.
I don't know if it's already too late, but if it isn't:
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
--D
>
> 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.blocksize
>
> [1/1] docs:filesystems: fix spelling and grammar mistakes in iomap design page
> https://git.kernel.org/vfs/vfs/c/b1daf3f8475f
prev parent reply other threads:[~2024-09-17 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-08 17:28 [PATCH] docs:filesystems: fix spelling and grammar mistakes in iomap design page Dennis Lam
2024-09-09 7:53 ` Christian Brauner
2024-09-17 16:17 ` Darrick J. Wong [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=20240917161749.GD182218@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=dennis.lamerice@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.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).