From: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
To: Qiang Zhao <qiang.zhao@nxp.com>,
"Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
Cc: linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] soc: fsl: qe: Fix sparse warnings in GPIO
Date: Mon, 7 Sep 2026 22:54:35 +0200 [thread overview]
Message-ID: <178881446326.32908.2707847448430333820.b4-ty@kernel.org> (raw)
In-Reply-To: <6a84b38e766729676b375c93bf54c67ea455288d.1786080840.git.chleroy@kernel.org>
On Fri, 07 Aug 2026 07:35:52 +0200, Christophe Leroy (CS GROUP) wrote:
> A C=2 build on mpc83xx_defconfig provides following warnings:
>
> drivers/soc/fsl/qe/gpio.c:44:34: warning: incorrect type in assignment (different base types)
> drivers/soc/fsl/qe/gpio.c:44:34: expected restricted __be32 [usertype] cpdata
> drivers/soc/fsl/qe/gpio.c:44:34: got unsigned int [usertype] cpdata
> drivers/soc/fsl/qe/gpio.c:45:34: warning: incorrect type in assignment (different base types)
> drivers/soc/fsl/qe/gpio.c:45:34: expected restricted __be32 [usertype] cpdir1
> drivers/soc/fsl/qe/gpio.c:45:34: got unsigned int
> drivers/soc/fsl/qe/gpio.c:46:34: warning: incorrect type in assignment (different base types)
> drivers/soc/fsl/qe/gpio.c:46:34: expected restricted __be32 [usertype] cpdir2
> drivers/soc/fsl/qe/gpio.c:46:34: got unsigned int
> drivers/soc/fsl/qe/gpio.c:47:34: warning: incorrect type in assignment (different base types)
> drivers/soc/fsl/qe/gpio.c:47:34: expected restricted __be32 [usertype] cppar1
> drivers/soc/fsl/qe/gpio.c:47:34: got unsigned int
> drivers/soc/fsl/qe/gpio.c:48:34: warning: incorrect type in assignment (different base types)
> drivers/soc/fsl/qe/gpio.c:48:34: expected restricted __be32 [usertype] cppar2
> drivers/soc/fsl/qe/gpio.c:48:34: got unsigned int
> drivers/soc/fsl/qe/gpio.c:49:33: warning: incorrect type in assignment (different base types)
> drivers/soc/fsl/qe/gpio.c:49:33: expected restricted __be32 [usertype] cpodr
> drivers/soc/fsl/qe/gpio.c:49:33: got unsigned int
> drivers/soc/fsl/qe/gpio.c:297:17: warning: restricted __be32 degrades to integer
> drivers/soc/fsl/qe/gpio.c:299:17: warning: restricted __be32 degrades to integer
> drivers/soc/fsl/qe/gpio.c:302:17: warning: restricted __be32 degrades to integer
> drivers/soc/fsl/qe/gpio.c:304:17: warning: restricted __be32 degrades to integer
> drivers/soc/fsl/qe/gpio.c:308:18: warning: restricted __be32 degrades to integer
> drivers/soc/fsl/qe/gpio.c:314:9: warning: restricted __be32 degrades to integer
>
> [...]
Applied, thanks!
[1/1] soc: fsl: qe: Fix sparse warnings in GPIO
commit: 5af2ccc8ec749d98d3d0bed4b9df25781d7f2d46
Best regards,
--
Christophe Leroy (CS GROUP) <chleroy@kernel.org>
prev parent reply other threads:[~2026-09-07 20:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 5:35 Christophe Leroy (CS GROUP)
2026-09-07 20:54 ` Christophe Leroy (CS GROUP) [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=178881446326.32908.2707847448430333820.b4-ty@kernel.org \
--to=chleroy@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lkp@intel.com \
--cc=qiang.zhao@nxp.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
all inboxes | Powered by JetHome®