linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	bwalle@suse.de, greg@kroah.com, hugh@veritas.com,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	haveblue@us.ibm.com
Subject: Re: linux-next: Tree for July 29
Date: Wed, 6 Aug 2008 20:40:49 -0700	[thread overview]
Message-ID: <20080807034049.GC3495@suse.de> (raw)
In-Reply-To: <20080807110844.a912483a.sfr@canb.auug.org.au>

On Thu, Aug 07, 2008 at 11:08:44AM +1000, Stephen Rothwell wrote:
> HI Greg,
> 
> On Wed, 30 Jul 2008 16:44:19 -0700 Greg KH <gregkh@suse.de> wrote:
> >
> > On Thu, Jul 31, 2008 at 09:41:05AM +1000, Stephen Rothwell wrote:
> > > Hi Andrew,
> > > 
> > > On Wed, 30 Jul 2008 13:04:19 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
> > > >
> > > > The offending patch has just got itself turfed from linux-next so my
> > > > fix now has nothing to fix.
> > > > 
> > > > We'll see what happens!
> > > 
> > > I will put Dave's patch back with yours on top of it (hoping that Greg
> > > will take your patch).
> > 
> > Greg will, it's in my queue.
> 
> This is still not in your patch series ...  summary email with patch
> repeated below.

Just went in about 3 hours ago :)

I merged it with the original, that's the best way to do it.

thanks,

greg k-h

  reply	other threads:[~2008-08-07  3:44 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-29  7:23 linux-next: Tree for July 29 Stephen Rothwell
2008-07-29  7:48 ` Fernando Luis Vázquez Cao
2008-07-29 14:45 ` Dominik Brodowski
2008-08-03 14:56   ` Stephen Rothwell
2008-08-04  7:58     ` Dominik Brodowski
2008-07-29 16:25 ` Bartlomiej Zolnierkiewicz
2008-07-29 18:16   ` Greg KH
2008-07-29 20:49     ` Hugh Dickins
2008-07-30  4:48       ` Greg KH
2008-07-30  7:06         ` Bernhard Walle
2008-07-30  9:19           ` Andrew Morton
2008-07-30 19:27             ` Bartlomiej Zolnierkiewicz
2008-07-30 20:04               ` Andrew Morton
2008-07-30 23:41                 ` Stephen Rothwell
2008-07-30 23:44                   ` Greg KH
2008-08-07  1:08                     ` Stephen Rothwell
2008-08-07  3:40                       ` Greg KH [this message]
2008-08-07  6:10                         ` Stephen Rothwell
2008-07-30  1:05   ` linux-next: usb tree fix (Was: Re: linux-next: Tree for July 29) Stephen Rothwell
2008-07-30 19:38     ` Bartlomiej Zolnierkiewicz
  -- strict thread matches above, loose matches on Subject: below --
2009-07-29  7:36 linux-next: Tree for July 29 Stephen Rothwell
2010-07-29  4:32 Stephen Rothwell
2011-07-29  7:38 Stephen Rothwell
2011-07-30 11:38 ` Sedat Dilek
2011-07-30 16:08   ` Arnaud Lacombe
2011-07-30 16:16     ` Sedat Dilek

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=20080807034049.GC3495@suse.de \
    --to=gregkh@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=bwalle@suse.de \
    --cc=bzolnier@gmail.com \
    --cc=greg@kroah.com \
    --cc=haveblue@us.ibm.com \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).