From: Chris Down <chris@chrisdown.name>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Petr Mladek <pmladek@suse.com>
Subject: Re: arch/parisc/math-emu/driver.c:88:17: sparse: sparse: Using plain integer as NULL pointer
Date: Sun, 17 Jul 2022 08:11:15 +0100 [thread overview]
Message-ID: <YtO2E1+0sMFb+3VO@chrisdown.name> (raw)
In-Reply-To: <YtOwNiF1JJK544bN@chrisdown.name>
Oh, looks like that's already fixed by commit 7f2dcc7371c1 ("parisc: math-emu:
Avoid "fmt" macro collision"). I don't know why the sparse warning is still
there then, but moving to _printk certainly fixes it. I'll try to work out why
before sending the patch to at least give a reasonable changelog.
next prev parent reply other threads:[~2022-07-17 7:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 5:00 arch/parisc/math-emu/driver.c:88:17: sparse: sparse: Using plain integer as NULL pointer kernel test robot
2022-07-17 6:46 ` Chris Down
2022-07-17 7:11 ` Chris Down [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-12 18:55 kernel test robot
2022-08-07 6:34 kernel test robot
2022-04-27 0:11 kernel test robot
2022-02-13 1:46 kernel test robot
2021-12-05 11:52 kernel test robot
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=YtO2E1+0sMFb+3VO@chrisdown.name \
--to=chris@chrisdown.name \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=pmladek@suse.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