From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-next@vger.kernel.org
Subject: bisect of ARM - implicit declaration of function 'arch_irqs_disabled'
Date: Tue, 2 Jun 2015 21:51:26 -0400 [thread overview]
Message-ID: <20150603015125.GJ29898@windriver.com> (raw)
Hi Arnd,
While testing linux-next and some stuff I have pending, I came across a
build fail that I then found was also in Jun2 linux-next:
http://kisskb.ellerman.id.au/kisskb/buildresult/12435853/
A quick bisect leads to:
make[1]: Leaving directory '/home/paul/builds/arm-efm32_defconfig'
cb1293e2f594558ccc3995acf9c9d7400b3add36 is the first bad commit
commit cb1293e2f594558ccc3995acf9c9d7400b3add36
Author: Arnd Bergmann <arnd@arndb.de>
Date: Tue May 26 15:40:44 2015 +0100
ARM: 8375/1: disable some options on ARMv7-M
A google search led me to this:
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/320678.html
...but I did not see that in linux-next.
Anyway just a heads up on what I found. I have not investigated
further than that.
Paul.
--
reply other threads:[~2015-06-03 1:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150603015125.GJ29898@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=arnd@arndb.de \
--cc=linux-next@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).