linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Dhananjay Ugwekar <dhananjay.ugwekar@amd.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the tip tree with the pm tree
Date: Thu, 15 May 2025 17:49:12 +0200	[thread overview]
Message-ID: <aCYM-A_PYHK2kjSd@gmail.com> (raw)
In-Reply-To: <8c4ab851-1853-442e-90a9-225be16c804c@amd.com>


* Mario Limonciello <mario.limonciello@amd.com> wrote:

> On 5/12/2025 12:23 AM, Stephen Rothwell wrote:
> > Hi all,
> > 
> > On Mon, 12 May 2025 14:55:17 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > > 
> > > Today's linux-next merge of the tip tree got a conflict in:
> > > 
> > >    drivers/cpufreq/amd-pstate.c
> > > 
> > > between commit:
> > > 
> > >    608a76b65288 ("cpufreq/amd-pstate: Add support for the "Requested CPU Min frequency" BIOS option")
> > > 
> > > from the pm tree and commit:
> > > 
> > >    d7484babd2c4 ("x86/msr: Rename 'rdmsrl_on_cpu()' to 'rdmsrq_on_cpu()'")
> > > 
> > > from the tip tree.
> > > 
> > > I fixed it up (the former removed a line updated by the latter) and can
> > > carry the fix as necessary. This is now fixed as far as linux-next is
> > > concerned, but any non trivial conflicts should be mentioned to your
> > > upstream maintainer when your tree is submitted for merging.  You may
> > > also want to consider cooperating with the maintainer of the conflicting
> > > tree to minimise any particularly complex conflicts.
> > 
> > Actually it needed the fix up below.
> > 
> 
> Ingo,
> 
> Can you guys make an immutable branch for Rafael to merge into linux-pm for
> this change?
> 
> I can redo the amd-pstate merge based on that immutable branch.
> 
> Rafael,
> 
> If you want to just carry the fixup that's fine too.  Just LMK what you
> need.

If it's only about rdmsrl_on_cpu(), how about the simple compatibility 
wrapper below instead, applied to the x86 tree?

Can merge it into -tip and tomorrow's -next would resolve this without 
any changes or merges done to the PM tree.

Thanks,

	Ingo

===============>
 arch/x86/include/asm/msr.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/x86/include/asm/msr.h b/arch/x86/include/asm/msr.h
index a9ce56fc8785..4096b8af4ba7 100644
--- a/arch/x86/include/asm/msr.h
+++ b/arch/x86/include/asm/msr.h
@@ -329,6 +329,7 @@ static inline int wrmsr_safe_regs_on_cpu(unsigned int cpu, u32 regs[8])
 /* Compatibility wrappers: */
 #define rdmsrl(msr, val) rdmsrq(msr, val)
 #define wrmsrl(msr, val) wrmsrq(msr, val)
+#define rdmsrl_on_cpu(cpu, msr, q) rdmsrq_on_cpu(cpu, msr, q)
 
 #endif /* __ASSEMBLER__ */
 #endif /* _ASM_X86_MSR_H */

  reply	other threads:[~2025-05-15 15:49 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-12  4:55 linux-next: manual merge of the tip tree with the pm tree Stephen Rothwell
2025-05-12  5:23 ` Stephen Rothwell
2025-05-12 20:45   ` Mario Limonciello
2025-05-15 15:49     ` Ingo Molnar [this message]
2025-05-15 15:50       ` Mario Limonciello
2025-05-15 16:01         ` [PATCH] x86/msr: Add rdmsrl_on_cpu() compatibility wrapper Ingo Molnar
2025-05-28  3:50   ` linux-next: manual merge of the tip tree with the pm tree Stephen Rothwell
2025-05-28 14:14     ` Limonciello, Mario
2025-05-28 22:12       ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2025-05-16  6:15 Stephen Rothwell
2025-05-16  7:54 ` Ingo Molnar
2025-05-16  9:54   ` Stephen Rothwell
2025-05-16 12:45     ` Ingo Molnar
2025-05-28  3:52 ` Stephen Rothwell
2025-05-01  3:58 Stephen Rothwell
2025-05-06 15:07 ` Wysocki, Rafael J
2025-05-06 17:43   ` Ingo Molnar
2025-04-17  3:43 Stephen Rothwell
2025-04-17 11:22 ` Ingo Molnar
2024-07-02  4:15 Stephen Rothwell
2024-07-02  9:25 ` Borislav Petkov
2024-07-17  1:41 ` Stephen Rothwell
2024-07-17  2:33   ` srinivas pandruvada
2024-07-17  9:49     ` Borislav Petkov
2024-06-24 17:06 Mark Brown
2024-06-25  3:00 ` Xiaojian Du
2024-06-25  4:25   ` Borislav Petkov
2024-06-25  4:51     ` Xiaojian Du
2021-02-17  5:07 Stephen Rothwell
2021-02-17 10:15 ` Andy Shevchenko
2021-02-22  0:34 ` Stephen Rothwell
2018-10-08  2:44 Stephen Rothwell
2018-10-08 10:06 ` Rafael J. Wysocki
2018-10-08 10:34   ` Andy Shevchenko
2018-10-08  2:40 Stephen Rothwell
2018-10-08 10:05 ` Rafael J. Wysocki
2018-10-08 10:41   ` Andy Shevchenko
2018-03-23  2:20 Stephen Rothwell
2018-03-23  6:09 ` Ingo Molnar
2018-03-23 21:09   ` Rafael J. Wysocki
2018-03-24  8:15     ` Ingo Molnar
2017-11-06  2:10 Stephen Rothwell
2017-11-06 13:09 ` Rafael J. Wysocki
2017-08-11  4:06 Stephen Rothwell
2017-09-04  4:43 ` Stephen Rothwell
2016-11-22  5:48 Stephen Rothwell
2016-06-09  4:34 Stephen Rothwell
2016-04-19  2:59 Stephen Rothwell
2016-03-15  1:55 Stephen Rothwell
2016-03-11  1:57 Stephen Rothwell
2016-03-11 13:51 ` Rafael J. Wysocki
2016-02-29  4:42 Stephen Rothwell
2015-10-06  3:07 Stephen Rothwell
2015-03-31  7:58 Stephen Rothwell
2015-03-31 22:23 ` Rafael J. Wysocki
2015-03-31  7:10 Stephen Rothwell
2014-12-15  2:30 Stephen Rothwell
2014-11-25  5:46 Stephen Rothwell
2014-11-25 21:16 ` Rafael J. Wysocki
2014-08-04  6:55 Stephen Rothwell
2014-05-09  4:49 Stephen Rothwell
2014-01-13  3:29 Stephen Rothwell
2014-01-07  4:20 Stephen Rothwell
2014-01-06  7:18 Stephen Rothwell
2013-08-19  4:09 Stephen Rothwell
2013-04-11  4:08 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=aCYM-A_PYHK2kjSd@gmail.com \
    --to=mingo@kernel.org \
    --cc=dhananjay.ugwekar@amd.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=peterz@infradead.org \
    --cc=rjw@rjwysocki.net \
    --cc=sfr@canb.auug.org.au \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).