From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Git pull request: ARM LPC32XX architecture
Date: Tue, 27 Jul 2010 17:49:45 +0100 [thread overview]
Message-ID: <20100727164945.GD17099@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20100727164540.GC17099@n2100.arm.linux.org.uk>
On Tue, Jul 27, 2010 at 05:45:40PM +0100, Russell King - ARM Linux wrote:
> On Tue, Jul 27, 2010 at 06:19:36PM +0200, Kevin Wells wrote:
> > I just wanted to drop a friendly reminder on this pull request. As
> > of yesterday, everything still built fine with the latest tree, but
> > it's in need of some updates. Can you still pull this and I'll apply
> > the updates in another patch series in the next week?
>
> Yes, with one change - the defconfig needs attention. Uwe has a tool
> which can be used to compress it.
>
> Even so, I don't think we want, at this stage, to antagonise Linus
> by adding a new defconfig - we already have more than too many.
You'll also need at some point to add an apb_pclk clock (can be a dummy)
as the amba infrastructure will want it.
next prev parent reply other threads:[~2010-07-27 16:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 20:44 Git pull request: ARM LPC32XX architecture Kevin Wells
2010-03-12 21:03 ` Russell King - ARM Linux
2010-03-13 15:50 ` Robert Schwebel
2010-03-14 15:00 ` Russell King - ARM Linux
2010-03-30 16:53 ` Kevin Wells
2010-05-25 15:27 ` Kevin Wells
2010-05-25 17:21 ` Russell King - ARM Linux
2010-05-26 23:10 ` Kevin Wells
2010-07-27 16:19 ` Kevin Wells
2010-07-27 16:45 ` Russell King - ARM Linux
2010-07-27 16:49 ` Russell King - ARM Linux [this message]
2010-07-27 20:00 ` Kevin Wells
2010-07-27 21:44 ` Russell King - ARM Linux
2010-07-28 18:47 ` Kevin Wells
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=20100727164945.GD17099@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).