mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Christian Loehle <christian.loehle@arm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Sumeet Pawnikar <sumeet4linux@gmail.com>
Subject: linux-next: manual merge of the cpufreq-arm tree with the pm tree
Date: Tue, 22 Sep 2026 11:59:40 +0200	[thread overview]
Message-ID: <arJRjM9WBBjuXdHG@sirena.co.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 1749 bytes --]

Hi all,

Today's linux-next merge of the cpufreq-arm tree got a conflict in:

  drivers/cpufreq/cppc_cpufreq.c

between commit:

  995e7d4680706 ("cpufreq: CPPC: Create the FIE worker before enabling PCC callbacks")

from the pm tree and commit:

  d82d896f00e7b ("cpufreq: Use %pe to print error pointers symbolically")

from the cpufreq-arm tree.

I fixed it up (see below) 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.

diff --cc drivers/cpufreq/cppc_cpufreq.c
index 09e55bfdca885,f767898ebfb57..0000000000000
--- a/drivers/cpufreq/cppc_cpufreq.c
+++ b/drivers/cpufreq/cppc_cpufreq.c
@@@ -240,19 -228,16 +240,19 @@@ static int cppc_fie_kworker_init(void
  	};
  	int ret;
  
 -	kworker_fie = kthread_run_worker(0, "cppc_fie");
 -	if (IS_ERR(kworker_fie)) {
 +	guard(mutex)(&cppc_fie_lock);
 +
 +	if (kworker_fie)
 +		return 0;
 +
 +	worker = kthread_run_worker(0, "cppc_fie");
 +	if (IS_ERR(worker)) {
- 		pr_warn("%s: failed to create kworker_fie: %ld\n", __func__,
- 			PTR_ERR(worker));
+ 		pr_warn("%s: failed to create kworker_fie: %pe\n", __func__,
 -			kworker_fie);
 -		fie_disabled = FIE_DISABLED;
 -		kworker_fie = NULL;
 -		return;
++			worker);
 +		return PTR_ERR(worker);
  	}
  
 -	ret = sched_setattr_nocheck(kworker_fie->task, &attr);
 +	ret = sched_setattr_nocheck(worker->task, &attr);
  	if (ret) {
  		pr_warn("%s: failed to set SCHED_DEADLINE: %d\n", __func__,
  			ret);

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2026-09-22  9:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-22  9:59 Mark Brown [this message]
2026-09-22 17:43 ` Wysocki, Rafael J
  -- strict thread matches above, loose matches on Subject: below --
2025-02-06  0:50 Stephen Rothwell
2025-02-06  3:35 ` Viresh Kumar

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=arJRjM9WBBjuXdHG@sirena.co.uk \
    --to=broonie@kernel.org \
    --cc=christian.loehle@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=sumeet4linux@gmail.com \
    --cc=viresh.kumar@linaro.org \
    /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

all inboxes | Powered by JetHome®