public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Greg KH <greg@kroah.com>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for June 29
Date: Thu, 30 Jun 2011 02:49:53 +1000	[thread overview]
Message-ID: <20110630024953.de9c84af.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20110629141806.GB16986@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 888 bytes --]

Hi Greg,

On Wed, 29 Jun 2011 07:18:06 -0700 Greg KH <greg@kroah.com> wrote:
>
> On Wed, Jun 29, 2011 at 04:24:54PM +1000, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Changes since 20110628:
> > 
> > My fixes tree is empty again (the early part of mmotm-2011-06-22-13-05 is
> > mostly now included in Linus' tree and the experiment failed anyway :-))
> 
> Did it fail?  I thought it at least solved the build errors that people
> were seeing in the staging tree in other arches, allowing them to move
> on to other, "real" issues that they had.

The experiment was the start of getting parts of Andrew's tree into
linux-next - the fix patches were a side effect (they are now in Linus'
tree).  Hopefully, the experiment will continue in another fashion soon.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2011-06-29 16:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-29  6:24 linux-next: Tree for June 29 Stephen Rothwell
2011-06-29 14:18 ` Greg KH
2011-06-29 16:49   ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-06-29  7:53 Stephen Rothwell
2010-06-29  5:19 Stephen Rothwell
2009-06-29  6:48 Stephen Rothwell

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=20110630024953.de9c84af.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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