linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Miklos Szeredi <mszeredi@redhat.com>
Cc: Christian Brauner <brauner@kernel.org>,
	linux-api@vger.kernel.org, linux-man@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	Karel Zak <kzak@redhat.com>,
	linux-fsdevel@vger.kernel.org, Ian Kent <raven@themaw.net>,
	David Howells <dhowells@redhat.com>,
	Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH 0/4] listmount changes
Date: Wed, 29 Nov 2023 10:52:12 +0100	[thread overview]
Message-ID: <20231129-rinnen-gekapert-c3875be7c9da@brauner> (raw)
In-Reply-To: <20231128160337.29094-1-mszeredi@redhat.com>

On Tue, 28 Nov 2023 17:03:31 +0100, Miklos Szeredi wrote:
> This came out from me thinking about the best libc API.  It contains a few
> changes that simplify and (I think) improve the interface.
> 
> Tree:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git#vfs.mount
> 
> [...]

Afaict, all changes as discussed. Thanks. I folded the fixes into the
main commit. Links to the patches that were folded are in the commit
message and explained in there as well. The final commit is now rather
small and easy to read.

---

Applied to the vfs.mount branch of the vfs/vfs.git tree.
Patches in the vfs.mount 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.mount

[1/4] listmount: rip out flags
      https://git.kernel.org/vfs/vfs/c/735b1c55d14a (folded)
[2/4] listmount: list mounts in ID order
      https://git.kernel.org/vfs/vfs/c/735b1c55d14a (folded)
[3/4] listmount: small changes in semantics
      https://git.kernel.org/vfs/vfs/c/735b1c55d14a (folded)
[4/4] listmount: allow continuing
      https://git.kernel.org/vfs/vfs/c/735b1c55d14a (folded)

  parent reply	other threads:[~2023-11-29  9:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-28 16:03 [PATCH 0/4] listmount changes Miklos Szeredi
2023-11-28 16:03 ` [PATCH 1/4] listmount: rip out flags Miklos Szeredi
2023-11-28 16:03 ` [PATCH 2/4] listmount: list mounts in ID order Miklos Szeredi
2023-11-28 16:03 ` [PATCH 3/4] listmount: small changes in semantics Miklos Szeredi
2023-12-06 19:58   ` Serge E. Hallyn
2023-12-06 20:24     ` Miklos Szeredi
2023-12-08 13:07       ` Christian Brauner
2023-11-28 16:03 ` [PATCH 4/4] listmount: allow continuing Miklos Szeredi
2023-11-29  9:52 ` Christian Brauner [this message]
2023-11-29 10:22   ` [PATCH 0/4] listmount changes Miklos Szeredi
2023-11-29 10:40     ` Christian Brauner

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=20231129-rinnen-gekapert-c3875be7c9da@brauner \
    --to=brauner@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=kzak@redhat.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=mszeredi@redhat.com \
    --cc=raven@themaw.net \
    --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).