linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Tony Breeds <tony@bakeyournoodle.com>
Cc: linuxppc-dev@ozlabs.org, Michael Neuling <mikey@neuling.org>,
	stable@kernel.org, Eric B Munson <emunson@mgebm.net>
Subject: Re: [PATCH stable-2.6.27] powerpc: Add more Power7 specific definitions
Date: Tue, 14 Feb 2012 07:42:50 +0100	[thread overview]
Message-ID: <20120214064250.GC5221@1wt.eu> (raw)
In-Reply-To: <20120213224418.GA22646@thor.bakeyournoodle.com>

Hi Tony,

On Tue, Feb 14, 2012 at 09:44:19AM +1100, Tony Breeds wrote:
> On Mon, Feb 13, 2012 at 07:35:28AM +0100, Willy Tarreau wrote:
> > On Mon, Feb 13, 2012 at 11:52:02AM +1100, Michael Neuling wrote:
> > > stable-2.6.27.60 added c24cb8e5 which uses PV_POWER7 but it's not
> > > defined.  Following patch adds these definitions.
> > 
> > Thank you for the report Michael, I have no PPC toolchain so I have
> > not tested this one. Added now.
> 
> Just pimping the cross toolchains I build:
> 	http://kernel.org/pub/tools/crosstool/files/bin/

Thanks for this pointer, it can indeed be quite useful from time to time,
especially to check gcc-related regressions.

That said, I'd rather not install a number of toolchains for systems
I can't test. I regularly build for i386/x86_64/arm with real configs
that I can boot a machine on when I have a doubt. Building random
configs do not always test all source code, especially on architectures
which support a wide variety of embedded platforms.

But I'm keeping the URL, Thanks :-)
Willy

      reply	other threads:[~2012-02-14  6:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-13  0:52 [PATCH stable-2.6.27] powerpc: Add more Power7 specific definitions Michael Neuling
2012-02-13  6:35 ` Willy Tarreau
2012-02-13  9:15   ` Michael Neuling
2012-02-13 22:44   ` Tony Breeds
2012-02-14  6:42     ` Willy Tarreau [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=20120214064250.GC5221@1wt.eu \
    --to=w@1wt.eu \
    --cc=emunson@mgebm.net \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mikey@neuling.org \
    --cc=stable@kernel.org \
    --cc=tony@bakeyournoodle.com \
    /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).