From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] i.MX common clock support
Date: Fri, 11 May 2012 17:31:45 +0200 [thread overview]
Message-ID: <20120511153145.GI27341@pengutronix.de> (raw)
In-Reply-To: <201205111527.15765.arnd@arndb.de>
On Fri, May 11, 2012 at 03:27:15PM +0000, Arnd Bergmann wrote:
> On Friday 11 May 2012, Sascha Hauer wrote:
> > On Fri, May 11, 2012 at 03:14:36PM +0000, Arnd Bergmann wrote:
> > > On Wednesday 09 May 2012, Sascha Hauer wrote:
> > > > Hi Arnd, Olof,
> > > >
> > > > Please pull the following i.MX common clock support branch for next.
> > > >
> > > > Same as with Shawns series this one depends on:
> > > >
> > > > git://git.linaro.org/people/mturquette/linux.git clk-next
> > > > http://ftp.arm.linux.org.uk/pub/linux/arm/kernel/git-cur/linux-arm.git clkdev
> > > >
> > >
> > > I've put all of those on the next/clock branch now.
> >
> > So do you want me to rebase my stuff on arm-soc/next/clock then?
> >
>
> I'm not sure if we're talking about the same things. I mean I've put
> pulledthe clk-next branch from Mike and the clkdev branch from Russell
> into the next/clock branch and pulled both your imx series and Shawn's
> mxs series on top into the same branch.
Yes, we are talking about the same thing. I immediately pulled arm-soc
and have found the dependencies but not the imx clock patches. Now they
are there \o/
Thanks
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2012-05-11 15:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 7:15 [GIT PULL] i.MX common clock support Sascha Hauer
2012-05-11 15:14 ` Arnd Bergmann
2012-05-11 15:19 ` Sascha Hauer
2012-05-11 15:27 ` Arnd Bergmann
2012-05-11 15:31 ` Sascha Hauer [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=20120511153145.GI27341@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.