From: Nathan Chancellor <nathan@kernel.org>
To: Christian Brauner <brauner@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kbuild@vger.kernel.org, David Sterba <dsterba@suse.com>
Subject: Re: [PATCH] fs/pipe: stop duplicating union pipe_index declaration
Date: Wed, 29 Oct 2025 10:38:28 -0700 [thread overview]
Message-ID: <20251029173828.GA1669504@ax162> (raw)
In-Reply-To: <20251029-redezeit-reitz-1fa3f3b4e171@brauner>
Hi Christian,
On Wed, Oct 29, 2025 at 02:41:06PM +0100, Christian Brauner wrote:
> On Thu, 23 Oct 2025 10:21:42 +0200, Rasmus Villemoes wrote:
> > Now that we build with -fms-extensions, union pipe_index can be
> > included as an anonymous member in struct pipe_inode_info, avoiding
> > the duplication.
> >
> >
>
> Applied to the vfs-6.19.misc branch of the vfs/vfs.git tree.
> Patches in the vfs-6.19.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-6.19.misc
>
> [1/1] fs/pipe: stop duplicating union pipe_index declaration
> https://git.kernel.org/vfs/vfs/c/ade24f8214fe
As you may have noticed since I do not actually see this pushed, this
change requires the '-fms-extensions' change that we are carrying in the
kbuild tree for 6.19.
https://git.kernel.org/kbuild/c/778740ee2d00e5c04d0c8ffd9c3beea89b1ec554
Would you be okay with us carrying this change there as well with your
Ack? Once '-fms-extensions' makes it into 6.19-rc1, you should be free
to make any other changes like this.
Cheers,
Nathan
next prev parent reply other threads:[~2025-10-29 17:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 8:21 [PATCH] fs/pipe: stop duplicating union pipe_index declaration Rasmus Villemoes
2025-10-23 16:44 ` Nathan Chancellor
2025-10-23 16:48 ` Linus Torvalds
2025-10-29 13:42 ` Christian Brauner
2025-10-29 13:41 ` Christian Brauner
2025-10-29 17:38 ` Nathan Chancellor [this message]
2025-10-29 22:25 ` Christian Brauner
2025-10-29 22:53 ` Linus Torvalds
2025-10-29 23:13 ` Christian Brauner
2025-10-29 23:30 ` Nathan Chancellor
2025-10-30 13:23 ` fms extension (Was: [PATCH] fs/pipe: stop duplicating union pipe_index declaration) Christian Brauner
2025-10-30 13:38 ` Ard Biesheuvel
2025-10-30 17:29 ` Nathan Chancellor
2025-10-30 20:16 ` Christian Brauner
2025-10-31 1:34 ` Nathan Chancellor
2025-11-01 13:10 ` Christian Brauner
2025-11-01 16:38 ` Nathan Chancellor
2025-11-06 22:09 ` Christian Brauner
2025-11-06 23:20 ` Nathan Chancellor
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=20251029173828.GA1669504@ax162 \
--to=nathan@kernel.org \
--cc=brauner@kernel.org \
--cc=dsterba@suse.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=torvalds@linux-foundation.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).