From: Greg KH <greg@kroah•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki•net>,
Viresh Kumar <viresh.kumar@linaro•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: Re: linux-next: duplicate patch in the driver-core tree
Date: Mon, 20 Feb 2023 08:13:19 +0100 [thread overview]
Message-ID: <Y/Mdj8q6jHugVSBn@kroah.com> (raw)
In-Reply-To: <20230220133847.11dacf2b@canb.auug.org.au>
On Mon, Feb 20, 2023 at 01:38:47PM +1100, Stephen Rothwell wrote:
> 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.
Thanks for the note, this should be fine, I didn't realize it ended up
in the opp tree as well, sorry about that.
greg k-h
next prev parent reply other threads:[~2023-02-20 7:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 2:38 linux-next: duplicate patch in the driver-core tree Stephen Rothwell
2023-02-20 7:13 ` 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-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=Y/Mdj8q6jHugVSBn@kroah.com \
--to=greg@kroah$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rjw@rjwysocki$(echo .)net \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=viresh.kumar@linaro$(echo .)org \
--cc=zhengqi.arch@bytedance$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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