From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "kernel test robot" <lkp@intel.com>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
linux-gpio@vger.kernel.org
Subject: Re: [linusw-pinctrl:for-next] BUILD REGRESSION 0c3c8458428ab471178a0d155222eaa62083d033
Date: Wed, 23 Mar 2022 17:46:55 +0100 [thread overview]
Message-ID: <YjtO/0zlcYPdFR59@latitude> (raw)
In-Reply-To: <CACRpkdb2hifdLLtquEMqty2hBzr8ap_HxZVNRq5GY5ed3kR3YA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1895 bytes --]
On Wed, Mar 23, 2022 at 04:05:02PM +0100, Linus Walleij wrote:
> Hi Jonathan,
>
> this driver just keeps creating new sparse warnings, I try to fix them
> but I wonder
> if new warnings will result everytime I fix something?
Hm, sorry about the chaos.
> Do you think you could run sparse over the drivers in some way and check
> what else needs to be fixed?
I ran "make C=1" on drivers/pinctrl/nuvoton now, and only noticed the
same array initializer syntax warning as in pinctrl-wpcm450, in pinctrl-npcm7xx.
>
> Yours,
> Linus Walleij
>
> On Wed, Mar 23, 2022 at 3:52 PM kernel test robot <lkp@intel.com> wrote:
> >
> > tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git for-next
> > branch HEAD: 0c3c8458428ab471178a0d155222eaa62083d033 pinctrl: nuvoton: Fix sparse warning
> >
> > Error/Warning reports:
> >
> > https://lore.kernel.org/linux-gpio/202203222145.UcCrXHfm-lkp@intel.com
> >
> > Unverified Error/Warning (likely false positive, please contact us if interested):
> >
> > drivers/pinctrl/nuvoton/pinctrl-wpcm450.c:470:26: error: array type has incomplete element type 'struct group_desc'
> > drivers/pinctrl/nuvoton/pinctrl-wpcm450.c:470:40: error: array has incomplete element type 'struct group_desc'
> > drivers/pinctrl/nuvoton/pinctrl-wpcm450.c:824:56: warning: parameter 'selector' set but not used [-Wunused-but-set-parameter]
> > drivers/pinctrl/nuvoton/pinctrl-wpcm450.c:888:48: warning: parameter 'group' set but not used [-Wunused-but-set-parameter]
This bunch was fixed with my patch "pinctrl: nuvoton: wpcm450: select
GENERIC_PINCTRL_GROUPS". There are also two more fixes sent by Jialin
Zhang and Dan Carpenter over the past week.
> > include/linux/build_bug.h:16:51: error: bit-field '<anonymous>' width not an integer constant
Unsure about this one.
Best regards,
Jonathan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-03-23 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 14:51 [linusw-pinctrl:for-next] BUILD REGRESSION 0c3c8458428ab471178a0d155222eaa62083d033 kernel test robot
2022-03-23 15:05 ` Linus Walleij
2022-03-23 16:46 ` Jonathan Neuschäfer [this message]
2022-03-24 0:33 ` Linus Walleij
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=YjtO/0zlcYPdFR59@latitude \
--to=j.neuschaefer@gmx.net \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=lkp@intel.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