From: Herve Codina <herve.codina@bootlin.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org,
Kent Overstreet <kent.overstreet@linux.dev>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
linux-bcache@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: Build regressions/improvements in v6.12-rc1
Date: Mon, 30 Sep 2024 18:26:33 +0200 [thread overview]
Message-ID: <20240930182633.6b5ce8ed@bootlin.com> (raw)
In-Reply-To: <6464b079-372d-d3f-d774-a7c05916fbe2@linux-m68k.org>
Hi Geert,
On Mon, 30 Sep 2024 17:11:09 +0200 (CEST)
Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> On Mon, 30 Sep 2024, Geert Uytterhoeven wrote:
> > Below is the list of build error/warning regressions/improvements in
> > v6.12-rc1[1] compared to v6.11[2].
...
powerpc-gcc13/ppc64_book3e_allmodconfig
>
> drivers/soc/fsl/qe/qmc.c: In function 'qmc_qe_init_resources':
> include/linux/err.h:28:49: error: cast to pointer from integer of different size [-Werror=int-to-pointer-cast]
> 28 | #define IS_ERR_VALUE(x) unlikely((unsigned long)(void *)(x) >= (unsigned long)-MAX_ERRNO)
> | ^
> include/linux/compiler.h:77:45: note: in definition of macro 'unlikely'
> 77 | # define unlikely(x) __builtin_expect(!!(x), 0)
> | ^
> drivers/soc/fsl/qe/qmc.c:1764:13: note: in expansion of macro 'IS_ERR_VALUE'
> 1764 | if (IS_ERR_VALUE(info)) {
> | ^~~~~~~~~~~~
>
> IS_ERR_VALUE() is meant for pointers (fix available)
I saw your patch, tested and acked it.
Thanks for the patch.
Hervé
prev parent reply other threads:[~2024-09-30 16:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHk-=wiwVOCZsC6a4dLdb1UjL2fS_CnLNjrPL0XGFbDd9C26Cg@mail.gmail.com>
[not found] ` <20240930145322.129875-1-geert@linux-m68k.org>
2024-09-30 15:11 ` Build regressions/improvements in v6.12-rc1 Geert Uytterhoeven
2024-09-30 16:26 ` Herve Codina [this message]
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=20240930182633.6b5ce8ed@bootlin.com \
--to=herve.codina@bootlin.com \
--cc=christophe.leroy@csgroup.eu \
--cc=geert@linux-m68k.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).