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: 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: Mon, 28 Apr 2025 11:57:04 +1000	[thread overview]
Message-ID: <20250428115704.46e31d9c@canb.auug.org.au> (raw)

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

Hi all,

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

error[E0308]: mismatched types
   --> rust/kernel/cpufreq.rs:950:18
    |
950 |             Some(Self::update_limits_callback)
    |             ---- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected fn pointer, found fn item
    |             |
    |             arguments to this enum variant are incorrect
    |
    = note: expected fn pointer `unsafe extern "C" fn(*mut bindings::cpufreq_policy)`
                  found fn item `extern "C" fn(u32) {cpufreq::Registration::<T>::update_limits_callback}`
help: the type constructed contains `extern "C" fn(u32) {cpufreq::Registration::<T>::update_limits_callback}` due to the type of the argument passed
   --> rust/kernel/cpufreq.rs:950:13
    |
950 |             Some(Self::update_limits_callback)
    |             ^^^^^----------------------------^
    |                  |
    |                  this argument influences the type of `Some`
note: tuple variant defined here
   --> /usr/lib/rustlib/src/rust/library/core/src/option.rs:580:5
    |
580 |     Some(#[stable(feature = "rust1", since = "1.0.0")] T),
    |     ^^^^

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0308`.

Caused by commit

  c490d1f07bec ("rust: cpufreq: Extend abstractions for driver registration")

I have used the cpufreq-arm tree from next-20250424 for today.

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2025-04-28  1:57 UTC|newest]

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