All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	PowerPC <linuxppc-dev@lists.ozlabs.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.current tree
Date: Fri, 12 Apr 2024 07:10:19 +0200	[thread overview]
Message-ID: <2024041201-shrug-carefully-c3a4@gregkh> (raw)
In-Reply-To: <87mspzci46.fsf@mail.lhotse>

On Fri, Apr 12, 2024 at 02:36:25PM +1000, Michael Ellerman wrote:
> Stephen Rothwell <sfr@canb.auug.org.au> writes:
> > Hi all,
> >
> > The following commit is also in the powerpc-fixes tree as a different
> > commit (but the same patch):
> >
> >   156539fd6501 ("Documentation: embargoed-hardware-issues.rst: Add myself for Power")
> >
> > This is commit
> >
> >   36627111b568 ("Documentation: embargoed-hardware-issues.rst: Add myself for Power")
> >
> > in the powerpc-fixes tree.
> 
> I can drop my version easily enough.

Either is fine, or both, it doesn't really matter :)

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	PowerPC <linuxppc-dev@lists.ozlabs.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the driver-core.current tree
Date: Fri, 12 Apr 2024 07:10:19 +0200	[thread overview]
Message-ID: <2024041201-shrug-carefully-c3a4@gregkh> (raw)
In-Reply-To: <87mspzci46.fsf@mail.lhotse>

On Fri, Apr 12, 2024 at 02:36:25PM +1000, Michael Ellerman wrote:
> Stephen Rothwell <sfr@canb.auug.org.au> writes:
> > Hi all,
> >
> > The following commit is also in the powerpc-fixes tree as a different
> > commit (but the same patch):
> >
> >   156539fd6501 ("Documentation: embargoed-hardware-issues.rst: Add myself for Power")
> >
> > This is commit
> >
> >   36627111b568 ("Documentation: embargoed-hardware-issues.rst: Add myself for Power")
> >
> > in the powerpc-fixes tree.
> 
> I can drop my version easily enough.

Either is fine, or both, it doesn't really matter :)

thanks,

greg k-h

  reply	other threads:[~2024-04-12  5:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-11 22:43 linux-next: duplicate patch in the driver-core.current tree Stephen Rothwell
2024-04-11 22:43 ` Stephen Rothwell
2024-04-12  4:36 ` Michael Ellerman
2024-04-12  4:36   ` Michael Ellerman
2024-04-12  5:10   ` Greg KH [this message]
2024-04-12  5:10     ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2025-01-07 20:02 Stephen Rothwell
2025-01-08  8:15 ` Greg KH
2025-04-15 23:44 Stephen Rothwell
2025-04-16  5:49 ` Greg KH

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=2024041201-shrug-carefully-c3a4@gregkh \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --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.