From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the driver-core tree
Date: Mon, 18 Dec 2023 11:26:08 +0100 [thread overview]
Message-ID: <2023121857-myself-contact-8ca8@gregkh> (raw)
In-Reply-To: <20231218173506.2165eef6@canb.auug.org.au>
On Mon, Dec 18, 2023 at 05:35:06PM +1100, Stephen Rothwell wrote:
> Hi Andrew,
>
> On Sun, 17 Dec 2023 21:54:29 -0800 Andrew Morton <akpm@linux-foundation.org> wrote:
> >
> > On Mon, 18 Dec 2023 15:40:34 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > > The following commit is also in the mm tree as a different commit (but
> > > the same patch):
> > >
> > > 2678fd2fe9ee ("initramfs: Expose retained initrd as sysfs file")
> > >
> > > This is commit
> > >
> > > 426081603f6c ("initramfs: expose retained initrd as sysfs file")
> > >
> > > in the mm tree.
> >
> > I'm suspecting that something went wrong here?
>
> Like what? You and Greg have applied the same patch. It happens.
Yeah, sorry about that, git should be able to handle this fine.
greg k-h
next prev parent reply other threads:[~2023-12-18 10:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 4:40 linux-next: duplicate patch in the driver-core tree Stephen Rothwell
2023-12-18 5:54 ` Andrew Morton
2023-12-18 6:35 ` Stephen Rothwell
2023-12-18 10:26 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-11 6:29 Stephen Rothwell
2025-07-11 6:48 ` Greg KH
2025-04-30 7:47 Stephen Rothwell
2025-04-30 18:34 ` Rafael J. Wysocki
2025-04-30 18:56 ` Greg KH
2023-02-20 2:38 Stephen Rothwell
2023-02-20 7:13 ` Greg KH
2023-02-14 1:57 Stephen Rothwell
2023-02-14 6:46 ` Greg KH
2023-02-14 16:47 ` Wysocki, Rafael J
2023-02-14 16:59 ` Greg KH
2023-02-20 12:16 ` 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=2023121857-myself-contact-8ca8@gregkh \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.