From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] imx6q cpuidle for 3.9
Date: Mon, 4 Feb 2013 22:25:34 -0800 [thread overview]
Message-ID: <20130205062534.GB13049@quad.lixom.net> (raw)
In-Reply-To: <20130205020344.GA11039@S2101-09.ap.freescale.net>
On Tue, Feb 05, 2013 at 10:03:47AM +0800, Shawn Guo wrote:
> On Wed, Jan 30, 2013 at 09:19:22PM +0800, Shawn Guo wrote:
> > On Tue, Jan 29, 2013 at 09:50:28AM -0800, Olof Johansson wrote:
> > > This has some small conflicts with the cleanup branch. Can you please base it
> > > on top of cleanup so we can avoid the merge conflicts when things go upstream?
> > > It's common to have the per-soc cleanup branches as bases for some of the
> > > feature branches just for this reason.
> > >
> > Ok, done as below.
> >
> Ping?
Yeah, sorry -- pulled now as imx/cpuidle, included in next/soc.
-Olof
prev parent reply other threads:[~2013-02-05 6:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 5:46 [GIT PULL] imx6q cpuidle for 3.9 Shawn Guo
2013-01-29 17:50 ` Olof Johansson
2013-01-30 13:19 ` Shawn Guo
2013-02-05 2:03 ` Shawn Guo
2013-02-05 6:25 ` Olof Johansson [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=20130205062534.GB13049@quad.lixom.net \
--to=olof@lixom.net \
--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