The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Chanwoo Choi <cw00.choi@samsung.com>
Cc: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
	"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 devfreq tree
Date: Mon, 12 May 2025 12:09:03 +1000	[thread overview]
Message-ID: <20250512120903.0c7aa9b7@canb.auug.org.au> (raw)

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

Hi all,

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

drivers/devfreq/sun8i-a33-mbus.c: In function 'sun8i_a33_mbus_probe':
drivers/devfreq/sun8i-a33-mbus.c:384:47: error: passing argument 1 of 'devm_clk_rate_exclusive_get' from incompatible pointer type [-Wincompatible-pointer-types]
  384 |         ret = devm_clk_rate_exclusive_get(priv->clk_mbus);
      |                                           ~~~~^~~~~~~~~~
      |                                               |
      |                                               struct clk *
In file included from drivers/devfreq/sun8i-a33-mbus.c:6:
include/linux/clk.h:214:48: note: expected 'struct device *' but argument is of type 'struct clk *'
  214 | int devm_clk_rate_exclusive_get(struct device *dev, struct clk *clk);
      |                                 ~~~~~~~~~~~~~~~^~~
drivers/devfreq/sun8i-a33-mbus.c:384:15: error: too few arguments to function 'devm_clk_rate_exclusive_get'
  384 |         ret = devm_clk_rate_exclusive_get(priv->clk_mbus);
      |               ^~~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/clk.h:214:5: note: declared here
  214 | int devm_clk_rate_exclusive_get(struct device *dev, struct clk *clk);
      |     ^~~~~~~~~~~~~~~~~~~~~~~~~~~

Caused by commit

  bc253b28a365 ("PM / devfreq: sun8i-a33-mbus: Simplify by using more devm functions")

I have used the devfreq tree from next-20250509 for today.

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2025-05-12  2:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-12  2:09 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-12-13  1:49 linux-next: build failure after merge of the devfreq tree Stephen Rothwell
2019-11-22  4:59 Stephen Rothwell
2019-11-22 21:54 ` Leonard Crestez

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=20250512120903.0c7aa9b7@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=cw00.choi@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=u.kleine-koenig@baylibre.com \
    /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