From: Christian Brauner <brauner@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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 14:37:50 +0200 [thread overview]
Message-ID: <20240909-armbinde-klaffen-fc59f67b2279@brauner> (raw)
In-Reply-To: <20240909-fahren-ansah-1b49bad59efd@brauner>
On Mon, Sep 09, 2024 at 02:19:20PM GMT, Christian Brauner wrote:
> On Mon, Sep 09, 2024 at 09:45:33PM GMT, Stephen Rothwell wrote:
> > 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")
>
> Sorry, I just pushed the fixed version now. Thanks for the patience.
Incidentally, is there a simple command to detect duplicate commits?
next prev parent reply other threads:[~2024-09-09 12:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 7:12 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
2024-09-09 12:19 ` Christian Brauner
2024-09-09 12:37 ` Christian Brauner [this message]
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=20240909-armbinde-klaffen-fc59f67b2279@brauner \
--to=brauner@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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
all inboxes | Powered by JetHome®