mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Viresh Kumar <viresh.kumar@linaro.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Aboorva Devarajan <aboorvad@linux.ibm.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>
Subject: linux-next: manual merge of the cpufreq-arm tree with the pm tree
Date: Thu, 6 Feb 2025 11:50:34 +1100	[thread overview]
Message-ID: <20250206115034.5d3004c6@canb.auug.org.au> (raw)

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

Hi all,

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

  drivers/cpufreq/cpufreq.c

between commit:

  0813fd2e14ca ("cpufreq: prevent NULL dereference in cpufreq_online()")

from the pm tree and commit:

  60208a700f76 ("cpufreq: Restrict enabling boost on policies with no boost frequencies")

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.

-- 
Cheers,
Stephen Rothwell

diff --cc drivers/cpufreq/cpufreq.c
index 30ffbddc7ece,3bb5cef263da..000000000000
--- a/drivers/cpufreq/cpufreq.c
+++ b/drivers/cpufreq/cpufreq.c
@@@ -1571,7 -1590,7 +1590,7 @@@ static int cpufreq_online(unsigned int 
  		policy->cdev = of_cpufreq_cooling_register(policy);
  
  	/* Let the per-policy boost flag mirror the cpufreq_driver boost during init */
- 	if (cpufreq_driver->set_boost &&
 -	if (policy->boost_supported &&
++	if (cpufreq_driver->set_boost && policy->boost_supported &&
  	    policy->boost_enabled != cpufreq_boost_enabled()) {
  		policy->boost_enabled = cpufreq_boost_enabled();
  		ret = cpufreq_driver->set_boost(policy, policy->boost_enabled);

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

             reply	other threads:[~2025-02-06  0:50 UTC|newest]

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

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=20250206115034.5d3004c6@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=aboorvad@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rjw@rjwysocki.net \
    --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®