From: Borislav Petkov <bp@suse.de>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org, tipbuild@zytor.com
Subject: Re: [tip:ras/core 2/2] drivers/ras/debugfs.c:9:5: error: redefinition of 'ras_userspace_consumers'
Date: Mon, 25 Mar 2019 08:19:48 +0100 [thread overview]
Message-ID: <20190325071948.GA14468@zn.tnic> (raw)
In-Reply-To: <5988.1553471781@turing-police>
On Sun, Mar 24, 2019 at 07:56:21PM -0400, Valdis Klētnieks wrote:
> On Mon, 25 Mar 2019 06:41:49 +0800, kbuild test robot said:
>
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git ras/core
> > head: 56baf8bd6c92819b1d89210fbfac2c6327a1271b
> > commit: 56baf8bd6c92819b1d89210fbfac2c6327a1271b [2/2] ras/debugfs: Fix -Wmissing-prototypes warnings
> > config: x86_64-randconfig-x003-201912 (attached as .config)
> > compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
>
> OK. Now to figure out why gcc-7.3 on Debian complains and gcc-9.0.1 on Fedora
> is perfectly happy with the patch, or if there's something I didn't expect in
> that randconfig, or if there's some other skew between what the test robot tree
> has in it, and next-20190318 (the last linux-next I built, which didn't
> complain...)
Ok, commit is gone from tip until this has been figured out.
Thx.
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
prev parent reply other threads:[~2019-03-25 7:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-24 22:41 [tip:ras/core 2/2] drivers/ras/debugfs.c:9:5: error: redefinition of 'ras_userspace_consumers' kbuild test robot
2019-03-24 23:56 ` Valdis Klētnieks
2019-03-25 7:19 ` Borislav Petkov [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=20190325071948.GA14468@zn.tnic \
--to=bp@suse.de \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tipbuild@zytor.com \
--cc=valdis.kletnieks@vt.edu \
/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