From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] i.MX6Q support
Date: Fri, 21 Oct 2011 20:01:58 +0200 [thread overview]
Message-ID: <20111021180158.GI23421@pengutronix.de> (raw)
In-Reply-To: <109937284.AlYUSiDe0P@wuerfel>
On Fri, Oct 21, 2011 at 12:23:33AM +0200, Arnd Bergmann wrote:
> On Thursday 20 October 2011 22:18:34 Russell King - ARM Linux wrote:
> > 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.
>
> Since I already had the branches at hand for the highbank tree, I
> gave this a go and rebased the imx6q branch on top of the stable branches
> that are there and confirmed that it actually builds.
>
> I have pulled the result into the next/soc branch along with highbank
> and picoxcell.
>
> Shawn and Sascha, can you confirm that this is correct?
Adding the following at least gives a compilable result. Works on i.MX3,
I couldn't test on i.MX6 though. BTW your patch exporting imx_ioremap is
missing in your for-next branch.
Sascha
next prev parent reply other threads:[~2011-10-21 18:01 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
2011-10-20 22:23 ` Arnd Bergmann
2011-10-21 18:01 ` Sascha Hauer [this message]
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=20111021180158.GI23421@pengutronix.de \
--to=s.hauer@pengutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.