From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the driver-core tree
Date: Mon, 11 Dec 2023 08:16:04 +0100 [thread overview]
Message-ID: <2023121114-gas-unstuffed-3045@gregkh> (raw)
In-Reply-To: <20231211152456.7526822b@canb.auug.org.au>
On Mon, Dec 11, 2023 at 03:24:56PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> The following commits are also in the pm tree tree as different
> commits (but the same patches):
>
> 3babbf614ae6 ("device property: fwnode_property_get_reference_args allows NULL args now")
> 1eaea4b3604e ("software node: Let args be NULL in software_node_get_reference_args")
> bef52aa0f3de ("acpi: property: Let args be NULL in __acpi_node_get_property_reference")
>
> These are commits
>
> a66cf024b377 ("device property: fwnode_property_get_reference_args() allows NULL args now")
> b912c6530332 ("software node: Let args be NULL in software_node_get_reference_args")
> cab48cbdfd27 ("ACPI: property: Let args be NULL in __acpi_node_get_property_reference()")
>
> in the pm tree.
Thanks for letting us know, I think git can handle the merge here ok.
greg k-h
next prev parent reply other threads:[~2023-12-11 7:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 4:24 linux-next: duplicate patches in the driver-core tree Stephen Rothwell
2023-12-11 7:16 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-16 4:12 Stephen Rothwell
2024-10-16 5:49 ` Greg KH
2023-08-15 11:34 Stephen Rothwell
2023-08-22 11:51 ` Greg KH
2023-02-02 1:12 Stephen Rothwell
2023-02-02 6:53 ` Sudeep Holla
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=2023121114-gas-unstuffed-3045@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox