From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Christian Brauner <brauner@kernel.org>
Cc: Vlastimil Babka <vbabka@suse.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the slab tree
Date: Mon, 9 Sep 2024 21:45:33 +1000 [thread overview]
Message-ID: <20240909214533.0f8437ef@canb.auug.org.au> (raw)
In-Reply-To: <20240909-kratzen-holzweg-c1fd7da1f895@brauner>
[-- Attachment #1: Type: text/plain, Size: 536 bytes --]
Hi Christian,
On Mon, 9 Sep 2024 13:02:03 +0200 Christian Brauner <brauner@kernel.org> wrote:
>
> Ok, how's it looking now?
I just fetched your tree. The top commit (vfs.all branch) is
a80a1ee241e7 ("Merge branch 'vfs.procfs' into vfs.all Signed-off-by: Christian Brauner <brauner@kernel.org>")
and commits
f2b8943e64a8 ("fs: pack struct file")
c0390d541128 ("fs: pack struct file")
are included. The first of those was in next-20240902 through today,
the second is new.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-09-09 11:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 7:12 linux-next: duplicate patches in the slab tree Stephen Rothwell
2024-09-09 7:18 ` Vlastimil Babka
2024-09-09 9:16 ` Christian Brauner
2024-09-09 9:40 ` Vlastimil Babka
2024-09-09 10:13 ` Christian Brauner
2024-09-09 10:35 ` Vlastimil Babka
2024-09-09 10:42 ` Christian Brauner
2024-09-09 11:02 ` Christian Brauner
2024-09-09 11:45 ` Stephen Rothwell [this message]
2024-09-09 12:19 ` Christian Brauner
2024-09-09 12:37 ` Christian Brauner
2024-09-09 13:44 ` Stephen Rothwell
2024-09-09 12:09 ` Vlastimil Babka
2024-09-09 12:18 ` Christian Brauner
2024-09-09 13:11 ` Konstantin Ryabitsev
2024-09-09 8:10 ` Stephen Rothwell
2024-09-09 8:32 ` Vlastimil Babka
2024-09-09 8:49 ` Vlastimil Babka
2024-09-09 9:33 ` Stephen Rothwell
2024-09-09 9:28 ` Stephen Rothwell
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=20240909214533.0f8437ef@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=brauner@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=vbabka@suse.cz \
/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