From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Request for holding Ryan's patch set for SPEAr
Date: Wed, 1 Sep 2010 08:49:04 +0100 [thread overview]
Message-ID: <20100901074904.GG8142@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <201008261258.40193.matthias.fuchs@esd.eu>
On Thu, Aug 26, 2010 at 12:58:39PM +0200, Matthias Fuchs wrote:
> Hi,
>
> did anything happen to this over the last two weeks?
Probably not because I've not been able to reply to this...
The proposal looks fine to me. However, bear in mind that we've shrunk
down the defconfigs already, and that's in mainline, so I suspect there's
still got a problem with them irrespective of whether Ryan's patches are
merged or not.
prev parent reply other threads:[~2010-09-01 7:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 6:34 Request for holding Ryan's patch set for SPEAr viresh kumar
2010-08-12 20:42 ` Ryan Mallon
2010-08-13 3:45 ` viresh kumar
2010-08-26 10:58 ` Matthias Fuchs
2010-08-26 11:20 ` viresh kumar
2010-09-01 7:49 ` 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=20100901074904.GG8142@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).