public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rob Herring (Arm)" <robh@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the cpufreq-arm tree
Date: Fri, 2 Aug 2024 10:57:26 +1000	[thread overview]
Message-ID: <20240802105726.6ce93aa8@canb.auug.org.au> (raw)

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

Hi all,

After merging the cpufreq-arm tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:

In file included from include/linux/cpufreq.h:17,
                 from drivers/cpufreq/spear-cpufreq.c:17:
drivers/cpufreq/spear-cpufreq.c: In function 'spear_cpufreq_probe':
include/linux/of.h:1435:51: error: lvalue required as unary '&' operand
 1435 |                  of_prop_next_u32(_it.prop, NULL, &u)};                 \
      |                                                   ^
drivers/cpufreq/spear-cpufreq.c:201:9: note: in expansion of macro 'of_property_for_each_u32'
  201 |         of_property_for_each_u32(np, "cpufreq_tbl", &val)
      |         ^~~~~~~~~~~~~~~~~~~~~~~~
include/linux/of.h:1437:62: error: lvalue required as unary '&' operand
 1437 |              _it.item = of_prop_next_u32(_it.prop, _it.item, &u))
      |                                                              ^
drivers/cpufreq/spear-cpufreq.c:201:9: note: in expansion of macro 'of_property_for_each_u32'
  201 |         of_property_for_each_u32(np, "cpufreq_tbl", &val)
      |         ^~~~~~~~~~~~~~~~~~~~~~~~

Caused by commit

  e960bbac0af4 ("cpufreq: spear: Use of_property_for_each_u32() instead of open coding")

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2024-08-02  0:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-02  0:57 Stephen Rothwell [this message]
2024-08-02  5:43 ` linux-next: build failure after merge of the cpufreq-arm tree Viresh Kumar
  -- strict thread matches above, loose matches on Subject: below --
2025-04-28  1:57 Stephen Rothwell
2025-04-29  4:48 ` Viresh Kumar
2024-03-05  0:09 Stephen Rothwell
2024-03-05  4: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=20240802105726.6ce93aa8@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=robh@kernel.org \
    --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