public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: David Miller <davem@davemloft•net>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: Tree for September 1
Date: Thu, 2 Sep 2010 13:33:42 +1000	[thread overview]
Message-ID: <20100902133342.4d3206b9.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20100901.183835.219746796.davem@davemloft.net>

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

Hi Dave,

On Wed, 01 Sep 2010 18:38:35 -0700 (PDT) David Miller <davem@davemloft•net> wrote:
>
> From: Stephen Rothwell <sfr@canb•auug.org.au>
> Date: Wed, 1 Sep 2010 13:36:14 +1000
> 
> > The net tree still has its build failure for which I have reverted a
> > commit.
> 
> Stephen I'm about to commit the following to net-next-2.6 in the meantime
> to deal with that so you don't have to revert whilst Fujita works on
> the more cleaner solution.

OK, thanks.  I still reverted the commit today as I fetched your tree
before you committed this.

-- 
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:[~2010-09-02  3:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-01  3:36 linux-next: Tree for September 1 Stephen Rothwell
2010-09-01 16:41 ` [PATCH next&mainline] oprofile: fix build when CONFIG_PM is disabled Randy Dunlap
2010-09-01 16:50   ` Robert Richter
2010-09-01 16:57     ` Randy Dunlap
2010-09-01 19:33     ` Robert Richter
2010-09-01 16:52   ` Ingo Molnar
2010-09-02  1:38 ` linux-next: Tree for September 1 David Miller
2010-09-02  3:33   ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-09-01 10:03 Stephen Rothwell
2008-09-01  9:19 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=20100902133342.4d3206b9.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=davem@davemloft$(echo .)net \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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