From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: Boot breaks in -next from LEGACY to LINEAR conversion
Date: Tue, 17 Jul 2012 19:57:49 +0100 [thread overview]
Message-ID: <20120717185749.GJ4477@opensource.wolfsonmicro.com> (raw)
-next fails to boot for me today on my s3c64xx based systems. Walking
back to the last time I tried and bisecting likely branches I find that
commit 910139 (irqdomain: Replace LEGACY mapping with LINEAR) is the one
that introduces the build break. Unfortunately the boot fails before I
get a console which makes diagnosis somewhat more tricky than would be
ideal. Any ideas?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120717/b89437d7/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Paul Mundt <lethal@linux-sh.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Thomas Gleixner <tglx@linutronix.de>,
Rob Herring <rob.herring@calxeda.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Kukjin Kim <kgene.kim@samsung.com>
Subject: Boot breaks in -next from LEGACY to LINEAR conversion
Date: Tue, 17 Jul 2012 19:57:49 +0100 [thread overview]
Message-ID: <20120717185749.GJ4477@opensource.wolfsonmicro.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 378 bytes --]
-next fails to boot for me today on my s3c64xx based systems. Walking
back to the last time I tried and bisecting likely branches I find that
commit 910139 (irqdomain: Replace LEGACY mapping with LINEAR) is the one
that introduces the build break. Unfortunately the boot fails before I
get a console which makes diagnosis somewhat more tricky than would be
ideal. Any ideas?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2012-07-17 18:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 18:57 Mark Brown [this message]
2012-07-17 18:57 ` Boot breaks in -next from LEGACY to LINEAR conversion Mark Brown
2012-07-18 0:52 ` Paul Mundt
2012-07-18 0:52 ` Paul Mundt
2012-07-18 10:16 ` Mark Brown
2012-07-18 10:16 ` Mark Brown
2012-07-18 16:10 ` Mark Brown
2012-07-18 16:10 ` Mark Brown
2012-07-18 16:27 ` Grant Likely
2012-07-18 16:27 ` Grant Likely
2012-07-20 4:30 ` Grant Likely
2012-07-20 4:30 ` Grant Likely
2012-07-20 9:42 ` Mark Brown
2012-07-20 9:42 ` Mark Brown
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=20120717185749.GJ4477@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.