From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Pull request for i.MX
Date: Tue, 19 Oct 2010 20:00:29 +0100 [thread overview]
Message-ID: <20101019190029.GC10325@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20101019165004.GX28242@pengutronix.de>
On Tue, Oct 19, 2010 at 06:50:04PM +0200, Sascha Hauer wrote:
>
> Here's the updated pull request, without duplicated patches this
> time
>
> Sascha
>
> The following changes since commit b9969f6525c9c00b042441acb0e1c0ee95560b63:
>
> Merge branch 'devel-stable' into devel (2010-10-18 22:34:52 +0100)
Errrrr, no, I'm about to re-merge devel-stable into devel...
What's the reason for basing it on my tree? Could it be based on top
of your previous pull request base, or alternatively Linus' tree?
next prev parent reply other threads:[~2010-10-19 19:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 14:21 Pull request for i.MX Sascha Hauer
2010-10-19 15:20 ` Baruch Siach
2010-10-19 15:37 ` Sascha Hauer
2010-10-19 16:50 ` Sascha Hauer
2010-10-19 19:00 ` Russell King - ARM Linux [this message]
2010-10-19 20:04 ` Sascha Hauer
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=20101019190029.GC10325@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).