public inbox for linuxppc-dev@ozlabs.org
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Kumar Gala <kumar.gala@freescale.com>,
	jbaron@redhat.com, linux-kernel@vger.kernel.org,
	linuxppc-dev@ozlabs.org, Anton Blanchard <anton@samba.org>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH] powerpc: Add jump label support
Date: Tue, 09 Nov 2010 15:02:56 +1100	[thread overview]
Message-ID: <1289275376.21111.227.camel@concordia> (raw)
In-Reply-To: <1289274119.12418.79.camel@gandalf.stny.rr.com>

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

On Mon, 2010-11-08 at 22:41 -0500, Steven Rostedt wrote:
> On Tue, 2010-11-09 at 14:33 +1100, Michael Ellerman wrote:
> 
> > > You don't need this protection in a file that is not exported to user
> > > space.
> > 
> > Ah true. I'll respin after I've heard if anyone has tested it :)
> 
> Don't wait for me. I'm stuck debugging some other crap. Getting a 4.5
> PPC compiler working is very low on my priority list, unfortunately. :-(

No worries, testing is for sissies anyway.

There are 4.5.0 crosses on kernel.org, I think they're the same as the
ones I'm using, which seem to work on powerpc at least.

http://kernel.org/pub/tools/crosstool/files/bin/x86_64/4.5.0/

cheers


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2010-11-09  4:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-08  4:12 [PATCH] powerpc: Add jump label support Michael Ellerman
2010-11-08 14:18 ` Steven Rostedt
2010-11-09  3:33   ` Michael Ellerman
2010-11-09  2:35 ` Stephen Rothwell
2010-11-09  3:33   ` Michael Ellerman
2010-11-09  3:41     ` Steven Rostedt
2010-11-09  4:02       ` Michael Ellerman [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=1289275376.21111.227.camel@concordia \
    --to=michael@ellerman.id.au \
    --cc=anton@samba.org \
    --cc=davem@davemloft.net \
    --cc=jbaron@redhat.com \
    --cc=kumar.gala@freescale.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=rostedt@goodmis.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