From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Greg KH <greg@kroah•com>, "Rafael J. Wysocki" <rjw@rjwysocki•net>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: duplicate patches in the driver-core tree
Date: Mon, 11 Dec 2023 15:24:56 +1100 [thread overview]
Message-ID: <20231211152456.7526822b@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 735 bytes --]
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.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-12-11 4:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 4:24 Stephen Rothwell [this message]
2023-12-11 7:16 ` linux-next: duplicate patches in the driver-core tree Greg KH
-- 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=20231211152456.7526822b@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=greg@kroah$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rjw@rjwysocki$(echo .)net \
/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