From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Hans de Goede <hdegoede@redhat•com>, Mark Gross <markgross@kernel•org>
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 drivers-x86 tree
Date: Fri, 3 Feb 2023 08:34:55 +1100 [thread overview]
Message-ID: <20230203083455.7a8cdee0@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 920 bytes --]
Hi all,
The following commits are also in Linus Torvalds' tree as different
commits (but the same patches):
037d07aeef02 ("platform/x86/amd/pmf: Fix to update SPS default pprof thermals")
5cca42fb5578 ("platform/x86/amd/pmf: Fix to update SPS thermals when power supply change")
66dc77b5c2a7 ("platform/x86/amd: pmc: add CONFIG_SERIO dependency")
8b6ad2361561 ("platform/x86: thinkpad_acpi: Fix thinklight LED brightness returning 255")
9f093aff1dda ("platform/x86: touchscreen_dmi: Add Chuwi Vi8 (CWI501) DMI match")
a63149e5d662 ("platform/x86/amd/pmf: update to auto-mode limits only after AMT event")
b3c37edce7dc ("platform/x86/amd/pmf: Add helper routine to update SPS thermals")
c02576762825 ("platform/x86/amd/pmf: Add helper routine to check pprof is balanced")
f1db3f08b51d ("platform/x86/amd/pmf: Ensure mutexes are initialized before use")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-02-02 21:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 21:34 Stephen Rothwell [this message]
2023-02-03 9:14 ` linux-next: duplicate patches in the drivers-x86 tree Hans de Goede
-- strict thread matches above, loose matches on Subject: below --
2025-03-25 6:23 Stephen Rothwell
2025-03-26 21:12 ` 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=20230203083455.7a8cdee0@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=hdegoede@redhat$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=markgross@kernel$(echo .)org \
/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