From: Christian Brauner <brauner@kernel.org>
To: Jan Kara <jack@suse.cz>
Cc: Christian Brauner <brauner@kernel.org>,
Dave Chinner <david@fromorbit.com>,
linux-fsdevel@vger.kernel.org, Al Viro <viro@ZenIV.linux.org.uk>,
David Howells <dhowells@redhat.com>
Subject: Re: [PATCH v2] fs: Provide helpers for manipulating sb->s_readonly_remount
Date: Mon, 19 Jun 2023 18:06:09 +0200 [thread overview]
Message-ID: <20230619-nutzt-textzeilen-0b0493a88185@brauner> (raw)
In-Reply-To: <20230619111832.3886-1-jack@suse.cz>
On Mon, 19 Jun 2023 13:18:32 +0200, Jan Kara wrote:
> Provide helpers to set and clear sb->s_readonly_remount including
> appropriate memory barriers. Also use this opportunity to document what
> the barriers pair with and why they are needed.
>
>
I'm traveling back from Vienna to Berlin today so will back online
completely tomorrow. This looks good to me now. Thanks for the nice
cleanup. Fwiw, it could've also waited until after the merge window but
now is obviously fine too.
---
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.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.misc
[1/1] fs: Provide helpers for manipulating sb->s_readonly_remount
https://git.kernel.org/vfs/vfs/c/5cf8f23baf5f
next prev parent reply other threads:[~2023-06-19 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 11:18 [PATCH v2] fs: Provide helpers for manipulating sb->s_readonly_remount Jan Kara
2023-06-19 16:06 ` Christian Brauner [this message]
2023-06-19 23:25 ` Dave Chinner
2023-06-20 11:30 ` Jan Kara
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=20230619-nutzt-textzeilen-0b0493a88185@brauner \
--to=brauner@kernel.org \
--cc=david@fromorbit.com \
--cc=dhowells@redhat.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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).