From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [FAILED] BLD phyCORE-i.MX31 + linux-next git kernel
Date: Sat, 17 Jul 2010 20:30:06 +0100 [thread overview]
Message-ID: <20100717193006.GA14791@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20100717191745.GC30077@pengutronix.de>
On Sat, Jul 17, 2010 at 09:17:45PM +0200, Uwe Kleine-K?nig wrote:
> Hello Russell,
>
> Our nightly built found a problem while working on linux-next.
> Commit v2.6.35-rc5-17-g6f7dd68 broke your devel branch
> by renaming lmb to memblock.
Yes, sfr and Mark Brown mentioned it yesterday. I fixed it yesterday,
but it's going to be until Monday-ish before linux-next gets sorted
(sfr is one of the sane folk who has weekends off!)
prev parent reply other threads:[~2010-07-17 19:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1OZs5K-0005Px-5r@himalia.hi.pengutronix.de>
2010-07-17 19:17 ` [FAILED] BLD phyCORE-i.MX31 + linux-next git kernel Uwe Kleine-König
2010-07-17 19:30 ` Russell King - ARM Linux [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=20100717193006.GA14791@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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 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).