From: Arnd Bergmann <arnd@arndb.de>
To: kernel test robot <lkp@intel.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [linux-next:pending-fixes 192/251] drivers/soc/ixp4xx/ixp4xx-npe.c:696:18: warning: format '%x' expects argument of type 'unsigned int', but argument 4 has type 'resource_size_t' {aka 'long long unsigned int'}
Date: Tue, 3 Aug 2021 10:06:47 +0200 [thread overview]
Message-ID: <CAK8P3a0z0bKRP4naz8URJEKwZOpiiqc9nZhz2z8c_d7RZ7szng@mail.gmail.com> (raw)
In-Reply-To: <202108031301.4AzM3lEd-lkp@intel.com>
On Tue, Aug 3, 2021 at 7:04 AM kernel test robot <lkp@intel.com> wrote:
>
> Hi Arnd,
>
> First bad commit (maybe != root cause):
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git pending-fixes
> head: be32e0f17dc184e41da2e83e5bf700f3f1c7e93f
> commit: 7f94b69ece515ac82defa60ef7cba2cf26180216 [192/251] ARM: ixp4xx: fix compile-testing soc drivers
> config: mips-randconfig-s032-20210803 (attached as .config)
> compiler: mips64-linux-gcc (GCC) 10.3.0
> reproduce:
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # apt-get install sparse
> # sparse version: v0.6.3-341-g8af24329-dirty
> # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=7f94b69ece515ac82defa60ef7cba2cf26180216
> git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git fetch --no-tags linux-next pending-fixes
> git checkout 7f94b69ece515ac82defa60ef7cba2cf26180216
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-10.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=mips
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
I had a fix for this in my randconfig test tree, turns out it was
never submitted.
Adding it now to my arm/fixes branch, and sending it to the list.
Arnd
next prev parent reply other threads:[~2021-08-03 8:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 5:04 kernel test robot
2021-08-03 8:06 ` Arnd Bergmann [this message]
2021-08-03 9:29 ` 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=CAK8P3a0z0bKRP4naz8URJEKwZOpiiqc9nZhz2z8c_d7RZ7szng@mail.gmail.com \
--to=arnd@arndb.de \
--cc=kbuild-all@lists.01.org \
--cc=linus.walleij@linaro.org \
--cc=linux-mm@kvack.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