All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Greg KH <greg@kroah.com>, "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Qi Zheng <zhengqi.arch@bytedance.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: duplicate patch in the driver-core tree
Date: Mon, 20 Feb 2023 13:38:47 +1100	[thread overview]
Message-ID: <20230220133847.11dacf2b@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 330 bytes --]

Hi all,

The following commit is also in the pm and opp trees as a different commit
(but the same patch):

  9f467f6375af ("OPP: fix error checking in opp_migrate_dentry()")

This is commit

  eca4c0eea534 ("OPP: fix error checking in opp_migrate_dentry()")

in the pm and opp trees.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2023-02-20  2:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-20  2:38 Stephen Rothwell [this message]
2023-02-20  7:13 ` linux-next: duplicate patch in the driver-core tree Greg KH
  -- 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-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-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=20230220133847.11dacf2b@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=greg@kroah.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=viresh.kumar@linaro.org \
    --cc=zhengqi.arch@bytedance.com \
    /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.