From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] i.MX6Q support
Date: Thu, 20 Oct 2011 22:18:34 +0100 [thread overview]
Message-ID: <20111020211834.GF21648@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20111020171158.GJ32007@S2100-06.ap.freescale.net>
On Fri, Oct 21, 2011 at 01:11:59AM +0800, Shawn Guo wrote:
> Please pull imx6q series. It's based on v3.1-rc10 with the following
> branches merged plus a number of cache-l2x0 patches currently sitting
> on rmk/for-next.
Don't do that. If there's something you need, _ask_ me. The L2x0
patches got shuffled out into their own branch when the SMP and debug
patches got split out of the 'misc' branch.
next prev parent reply other threads:[~2011-10-20 21:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 17:11 [GIT PULL] i.MX6Q support Shawn Guo
2011-10-20 21:18 ` Russell King - ARM Linux [this message]
2011-10-20 22:23 ` Arnd Bergmann
2011-10-21 18:01 ` Sascha Hauer
2011-10-22 0:58 ` Shawn Guo
2011-10-30 22:55 ` Arnd Bergmann
2011-10-24 1:15 ` Barry Song
2011-10-24 9:11 ` Russell King - ARM Linux
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=20111020211834.GF21648@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).