linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Huang Ying <ying.huang@intel.com>
To: dhowells <dhowells@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
	paulus <paulus@samba.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Andi Kleen <andi@firstfloor.org>,
	Russell King <rmk@arm.linux.org.uk>,
	Kyle McMartin <kyle@mcmartin.ca>, davem <davem@davemloft.net>,
	Linux-Arch <linux-arch@vger.kernel.org>,
	Matt Fleming <matt@console-pimps.org>
Subject: Re: [PATCH -tip -v4] irq_work: generic hard-irq context callbacks
Date: Thu, 16 Sep 2010 16:57:05 +0800	[thread overview]
Message-ID: <1284627425.2754.434.camel@yhuang-dev> (raw)
In-Reply-To: <1284539320.3764.266.camel@twins>

Hi, David,

On Wed, 2010-09-15 at 16:28 +0800, Peter Zijlstra wrote:
> FRV is one of those architectures that doesn't build a toolchain from
> plain gcc sources, David Howells did provide me with a toolchain for
> that, it does build, but really it should be getting its toolchain
> sorted upstream.

Where can I find latest FRV cross compiler workable for Linux kernel?

Best Regards,
Huang Ying


  parent reply	other threads:[~2010-09-16  8:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-13  6:50 [PATCH -tip -v4] irq_work: generic hard-irq context callbacks Huang Ying
2010-09-13  9:18 ` Peter Zijlstra
2010-09-13 10:32 ` Martin Schwidefsky
2010-09-13 11:36   ` Peter Zijlstra
2010-09-15  5:29     ` Huang Ying
2010-09-15  7:51       ` Martin Schwidefsky
2010-09-15  8:28       ` Peter Zijlstra
2010-09-15  8:50         ` Matt Fleming
2010-09-16  6:59           ` Huang Ying
2010-09-16  7:03             ` Paul Mundt
2010-09-16  8:57         ` Huang Ying [this message]
2010-09-17 12:37         ` David Howells
2010-09-23 20:12         ` David Howells
2010-09-26  0:40           ` Huang Ying
2010-09-26  7:32           ` David Howells
2010-09-15 15:10 Andi Kleen
2010-09-15 15:41 ` Peter Zijlstra
2010-09-15 19:30 ` Geert Uytterhoeven

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=1284627425.2754.434.camel@yhuang-dev \
    --to=ying.huang@intel.com \
    --cc=andi@firstfloor.org \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=hpa@zytor.com \
    --cc=kyle@mcmartin.ca \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@console-pimps.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --cc=peterz@infradead.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=schwidefsky@de.ibm.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).