From: Simon Horman <horms@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, dmaengine@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: Build regressions/improvements in v6.12-rc3
Date: Mon, 14 Oct 2024 11:29:00 +0100 [thread overview]
Message-ID: <20241014102900.GS77519@kernel.org> (raw)
In-Reply-To: <CAMuHMdWedOgc4S12FwQR8_80aqgRJ2pwrKWsNb5Svt6776ti3Q@mail.gmail.com>
On Mon, Oct 14, 2024 at 11:18:14AM +0200, Geert Uytterhoeven wrote:
> Hi Simon,
>
> On Mon, Oct 14, 2024 at 10:58 AM Simon Horman <horms@kernel.org> wrote:
> > On Mon, Oct 14, 2024 at 10:38:20AM +0200, Geert Uytterhoeven wrote:
> > > + /kisskb/src/drivers/net/ethernet/freescale/fs_enet/mii-bitbang.c: error: format '%x' expects argument of type 'unsigned int', but argument 4 has type 'resource_size_t {aka long long unsigned int}' [-Werror=format=]: => 126:37
> > > + /kisskb/src/drivers/net/ethernet/freescale/fs_enet/mii-bitbang.c: error: format '%x' expects argument of type 'unsigned int', but argument 4 has type 'resource_size_t' {aka 'long long unsigned int'} [-Werror=format=]: => 126:46
> >
> > I wonder what the correct string format is in these cases?
> > I didn't have a good idea the last time I looked.
>
> "%pa" + taking the address of the resource_size_t object.
>
> https://elixir.bootlin.com/linux/v6.11.3/source/Documentation/core-api/printk-formats.rst#L229
Thanks,
These format problems seem to have been introduced quite some time ago
by commit 9d9326d3bc0e ("phy: Change mii_bus id field to a string").
I'll send some patches to address the ones introduced by that patch
that I was able to still find in-tree.
next prev parent reply other threads:[~2024-10-14 10:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-13 21:46 Linux 6.12-rc3 Linus Torvalds
2024-10-14 7:27 ` Build regressions/improvements in v6.12-rc3 Geert Uytterhoeven
2024-10-14 8:38 ` Geert Uytterhoeven
2024-10-14 8:58 ` Simon Horman
2024-10-14 9:18 ` Geert Uytterhoeven
2024-10-14 10:29 ` Simon Horman [this message]
2024-10-16 2:00 ` Linux 6.12-rc3 Guenter Roeck
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=20241014102900.GS77519@kernel.org \
--to=horms@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.