public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Liam Girdwood <lg@opensource.wolfsonmicro.com>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.arm.linux.org.uk,
	broonie@opensource.wolfsonmicro.com, sfr@canb.auug.org.au,
	linux-next@vger.kernel.org
Subject: Re: [PATCH 0/13] Updated V4  - Regulator Framework
Date: Tue, 29 Jul 2008 13:40:43 -0700	[thread overview]
Message-ID: <20080729134043.d677323b.akpm@linux-foundation.org> (raw)
In-Reply-To: <1217363626.7498.47.camel@odin>

On Tue, 29 Jul 2008 21:33:46 +0100
Liam Girdwood <lg@opensource.wolfsonmicro.com> wrote:

> On Thu, 2008-07-10 at 02:08 -0700, Andrew Morton wrote:
> > On Fri, 02 May 2008 16:40:41 +0100 Liam Girdwood <lg@opensource.wolfsonmicro.com> wrote:
> > 
> > > This is an updated version of the kernel voltage & current regulator
> > > framework based on comments received from version 3 of the patch series.
> > 
> > git-regulator.patch has been in -mm for two months without incident.  I'd
> > forgotten about it.   This is bad - we should have put it into linux-next.
> > 
> > If you hope to get this into 2.6.27 then please send the git URL to Stephen
> > and the linux-next list asap.  Please also resend the patches to this list
> > for re-review.  Then, if it doesn't get shot down, send Linux a pull
> > request during the 2.6.27 merge window.  ie: about one week from today.
> 
> Would there be any chance of this going in for rc2 ? (2 pull requests
> sent recently prior to rc1) or would it be better now waiting for the
> 2.6.28 merge window ?
> 

Oh, I'd assumed that it had been merged already.

Linus was probably wondering "who is this Liam person and why is he
sending me stuff".  It should be OK for 2.6.27-rc1 unless Linus had
some specific reason for skipping it?  Please retry.

      reply	other threads:[~2008-07-29 20:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02 15:40 [PATCH 0/13] Updated V4 - Regulator Framework Liam Girdwood
2008-05-02 23:52 ` Andrew Morton
2008-05-03 10:31   ` Liam Girdwood
2008-05-08  6:35 ` Harald Welte
2008-05-08 20:16   ` Mark Brown
2008-05-08 20:51   ` Liam Girdwood
2008-05-09  4:37     ` Harald Welte
2008-05-09 19:44       ` Liam Girdwood
2008-05-11 14:39         ` Liam Girdwood
2008-07-10  9:08 ` Andrew Morton
2008-07-29 20:33   ` Liam Girdwood
2008-07-29 20:40     ` Andrew Morton [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=20080729134043.d677323b.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lg@opensource.wolfsonmicro.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.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