From: Randy Dunlap <rdunlap@infradead.org>
To: kbuild test robot <fengguang.wu@intel.com>,
Al Viro <viro@zeniv.linux.org.uk>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: fs/binfmt_flat.c:828:9: error: void value not ignored as it ought to be
Date: Sat, 2 Sep 2017 19:56:08 -0700 [thread overview]
Message-ID: <dddbc2b4-a2ca-c8a7-8933-dfb29d6986fb@infradead.org> (raw)
In-Reply-To: <201709030901.qU5Vfdmy%fengguang.wu@intel.com>
On 09/02/17 18:48, kbuild test robot wrote:
> Hi Al,
>
> FYI, the error/warning still remains.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: d0d6ab53c9abd7dd1070f43a0455328874127ba8
> commit: 468138d78510688fb5476f98d23f11ac6a63229a binfmt_flat: flat_{get,put}_addr_from_rp() should be able to fail
> date: 9 weeks ago
> config: m32r-mappi.nommu_defconfig (attached as .config)
> compiler: m32r-linux-gcc (GCC) 6.2.0
> reproduce:
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout 468138d78510688fb5476f98d23f11ac6a63229a
> # save the attached .config to linux build tree
> make.cross ARCH=m32r
>
>>> fs/binfmt_flat.c:828:9: error: void value not ignored as it ought to be
> ret = flat_put_addr_at_rp(rp, addr, relval);
> ^
Patch here for m32r and microblaze:
https://lkml.org/lkml/2017/7/30/179
Al, are these OK or is something more needed?
--
~Randy
next prev parent reply other threads:[~2017-09-03 2:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-03 1:48 kbuild test robot
2017-09-03 2:56 ` Randy Dunlap [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-08-19 23:27 kbuild test robot
2017-08-23 0:20 ` Randy Dunlap
2017-08-06 0:10 kbuild test robot
2017-07-30 2:33 kbuild test robot
2017-07-23 5:35 kbuild test robot
2017-07-23 15:03 ` Randy Dunlap
2017-07-16 22:54 kbuild 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=dddbc2b4-a2ca-c8a7-8933-dfb29d6986fb@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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®