From: Fengguang Wu <fengguang.wu@intel.com>
To: "Levin, Alexander" <alexander.levin@verizon.com>
Cc: "kbuild-all@01.org" <kbuild-all@01.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-stable-rc:linux-3.14.y 1941/4977] include/linux/irqdesc.h:80:33: error: 'NR_IRQS' undeclared here (not in a function)
Date: Mon, 12 Sep 2016 07:44:37 +0800 [thread overview]
Message-ID: <20160911234437.voyzdbxvvd2w5oqk@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <20160911204731.GB30805@sasha-lappy>
Hi Sasha,
On Sun, Sep 11, 2016 at 04:47:31PM -0400, Levin, Alexander wrote:
>On Sun, Sep 11, 2016 at 04:06:50PM -0400, kbuild test robot wrote:
>> Hi Sasha,
>>
>> FYI, the error/warning still remains.
>>
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-3.14.y
>> head: b65f2f457c49b2cfd7967c34b7a0b04c25587f13
>> commit: 017ff97daa4a7892181a4dd315c657108419da0c [1941/4977] kernel: add support for gcc 5
>
>Please make it stop :(
>
>I've introduced a commit to support gcc 5, and I'm guessing that in turn your build system now probably builds using gcc 5 for anything past that point, right?
Yes, many "hidden" error/warnings show up after that commit. I'll
ignore bisects to this commit.
>This causes new errors/warnings which appear to be caused by my commit, but obviously aren't.
>
>Can you please make the build system just ignore this commit if it gets bisected?
Yes, sure. Sorry for the noises!
Cheers,
Fengguang
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2016-09-11 23:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-11 20:06 kbuild test robot
2016-09-11 20:47 ` Levin, Alexander
2016-09-11 23:44 ` Fengguang Wu [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=20160911234437.voyzdbxvvd2w5oqk@wfg-t540p.sh.intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.levin@verizon.com \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
/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