All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	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: Wed, 30 Apr 2025 20:56:23 +0200	[thread overview]
Message-ID: <2025043005-default-hurray-7567@gregkh> (raw)
In-Reply-To: <4984921.GXAFRqVoOG@rjwysocki.net>

On Wed, Apr 30, 2025 at 08:34:39PM +0200, Rafael J. Wysocki wrote:
> On Wednesday, April 30, 2025 9:47:26 AM CEST Stephen Rothwell wrote:
> > Hi all,
> > 
> > The following commit is also in the pm tree as a different commit (but
> > the same patch):
> > 
> >   142ba31d8b4a ("PM: wakeup: Do not expose 4 device wakeup source APIs")
> > 
> > This is commit
> > 
> >   150b374b9ff9 ("PM: wakeup: Define four low-level functions as static")
> > 
> > in the pm tree.
> 
> I'll drop this from the PM tree, but this technically is PM material.
> 

Sorry about that, my fault.  I can revert it if that makes more sense.
Which ever you want is fine.

thanks,

greg k-h

  reply	other threads:[~2025-04-30 18:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-30  7:47 linux-next: duplicate patch in the driver-core tree Stephen Rothwell
2025-04-30 18:34 ` Rafael J. Wysocki
2025-04-30 18:56   ` 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
2023-12-18  4:40 Stephen Rothwell
2023-12-18  5:54 ` Andrew Morton
2023-12-18  6:35   ` Stephen Rothwell
2023-12-18 10:26     ` 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=2025043005-default-hurray-7567@gregkh \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --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.