public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek•org>
To: benh@kernel•crashing.org
Cc: Stephen Rothwell <sfr@canb•auug.org.au>, linux-next@vger•kernel.org
Subject: Re: linux-next: pci tree build failure
Date: Sat, 18 Oct 2008 15:41:00 -0700	[thread overview]
Message-ID: <200810181541.00638.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <1224131300.8157.536.camel@pasglop>

On Wednesday, October 15, 2008 9:28 pm Benjamin Herrenschmidt wrote:
> > Hm, I must have applied the wrong ones... but I didn't do a ppc build to
> > test. I'll fix it up.
>
> Thanks. So apply 1/2 from my orginal post and v3 of 2/2 that I sent
> yesterday. Let me know if you want me to just resend both.

No I've got them.  I must have accidentally dropped the 1/2 when I rebased 
last time, so d965c04f27d4df28b1ce77b0aea6329c07a8e13d is an orphan (btw 
Stephen how did you find it?).

Just test building & booting now, then I'll send Linus the pull request.

Thanks,
-- 
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2008-10-18 22:41 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-16  3:41 linux-next: pci tree build failure Stephen Rothwell
2008-10-16  3:44 ` Benjamin Herrenschmidt
2008-10-16  4:23   ` Jesse Barnes
2008-10-16  4:28     ` Benjamin Herrenschmidt
2008-10-18 22:41       ` Jesse Barnes [this message]
2008-10-19  4:15         ` Stephen Rothwell
2008-10-19  4:30           ` Jesse Barnes
  -- strict thread matches above, loose matches on Subject: below --
2010-01-27  6:49 Stephen Rothwell
2010-01-27 17:31 ` Jesse Barnes
2010-01-28  6:14   ` Stephen Rothwell
2010-01-18  8:40 Stephen Rothwell
2010-01-18 21:24 ` Rafael J. Wysocki
2010-01-19  2:35   ` Jesse Barnes
2010-01-19  3:19     ` Stephen Rothwell
2010-01-20  4:39 ` Jesse Barnes
2010-01-20  5:19   ` Stephen Rothwell
2010-01-04 22:55 Stephen Rothwell
2010-01-04 23:10 ` Matthew Wilcox
2010-01-04 23:48   ` Jesse Barnes
2010-01-05  3:41     ` Stephen Rothwell
2009-10-07  1:38 Stephen Rothwell
2009-10-07  1:45 ` Tejun Heo
2009-10-07 15:39   ` Jesse Barnes
2009-07-15  1:45 Stephen Rothwell
2009-07-15 16:09 ` Jesse Barnes
2009-07-15 23:46   ` Stephen Rothwell
2009-06-30  2:07 Stephen Rothwell
2009-06-30  2:13 ` Jesse Barnes
2009-06-30  2:24   ` Matthew Wilcox
2009-06-30 20:31     ` Jesse Barnes
2009-03-23  1:49 Stephen Rothwell
2009-03-25  1:21 ` Stephen Rothwell
2009-03-25  1:38   ` Jesse Barnes
2009-03-25  3:41     ` Stephen Rothwell
2009-03-25  4:30       ` Matthew Wilcox
2009-03-25 15:55         ` Jesse Barnes
2009-03-26  3:05           ` Stephen Rothwell
2009-03-26  3:37             ` Jesse Barnes
2009-03-26  4:54               ` Stephen Rothwell
2008-10-22  2:39 Stephen Rothwell
2008-10-22  3:47 ` Jesse Barnes
     [not found] <20080717130924.edd5a501.sfr@canb.auug.org.au>
2008-07-17 22:57 ` Rafael J. Wysocki
2008-07-18  6:09   ` Stephen Rothwell
2008-07-18  7:53     ` Ingo Molnar
2008-07-08  1:40 Stephen Rothwell
2008-07-08 14:54 ` Rafael J. Wysocki
     [not found] <20080630142314.34654d3c.sfr@canb.auug.org.au>
2008-06-30 14:11 ` Alan Stern
2008-07-02  2:11   ` Jesse Barnes
2008-06-30  5:11 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=200810181541.00638.jbarnes@virtuousgeek.org \
    --to=jbarnes@virtuousgeek$(echo .)org \
    --cc=benh@kernel$(echo .)crashing.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /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