All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Huang Ying <ying.huang@intel.com>
Cc: 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>, dhowells <dhowells@redhat.com>,
	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>DavidHowells
	<dhowells@redhat.com>
Subject: Re: [PATCH -tip -v4] irq_work: generic hard-irq context callbacks
Date: Wed, 15 Sep 2010 10:28:40 +0200	[thread overview]
Message-ID: <1284539320.3764.266.camel@twins> (raw)
In-Reply-To: <1284528590.2256.135.camel@yhuang-dev.sh.intel.com>

On Wed, 2010-09-15 at 13:29 +0800, Huang Ying wrote:

> I uses the cross build tool from:
> 
> http://www.kernel.org/pub/tools/crosstool/

I'm not familiar with those, I build my own gcc-4.5.1 toolchains for all
targets that would actually build a gcc toolchains, for those that don't
I simply don't care about.

> But I get compile errors on s390 and alpha even for tip/master
> (ce0c65112d37ff04016b4e0962a406281640739b). The build logs are attached.

I've got a patch to solve the Alpha issue, and I've got a patch for one
of the SH issues as well, but I understand you need to pull in Paul
Mundt's SH tree to make it fully build.

I've asked Ingo to merge the Alpha and SH patches I had pending.

> Do I use the wrong git tree? Or we should fix tip/master firstly?
> 
> And frv and sh have compile error even for linus/master and 2.6.35. So I
> can not compile test for these arches.

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.

WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: Huang Ying <ying.huang@intel.com>
Cc: 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>, dhowells <dhowells@redhat.com>,
	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>,
	DavidHowells <dhowells@redhat.com>
Subject: Re: [PATCH -tip -v4] irq_work: generic hard-irq context callbacks
Date: Wed, 15 Sep 2010 10:28:40 +0200	[thread overview]
Message-ID: <1284539320.3764.266.camel@twins> (raw)
In-Reply-To: <1284528590.2256.135.camel@yhuang-dev.sh.intel.com>

On Wed, 2010-09-15 at 13:29 +0800, Huang Ying wrote:

> I uses the cross build tool from:
> 
> http://www.kernel.org/pub/tools/crosstool/

I'm not familiar with those, I build my own gcc-4.5.1 toolchains for all
targets that would actually build a gcc toolchains, for those that don't
I simply don't care about.

> But I get compile errors on s390 and alpha even for tip/master
> (ce0c65112d37ff04016b4e0962a406281640739b). The build logs are attached.

I've got a patch to solve the Alpha issue, and I've got a patch for one
of the SH issues as well, but I understand you need to pull in Paul
Mundt's SH tree to make it fully build.

I've asked Ingo to merge the Alpha and SH patches I had pending.

> Do I use the wrong git tree? Or we should fix tip/master firstly?
> 
> And frv and sh have compile error even for linus/master and 2.6.35. So I
> can not compile test for these arches.

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.



  parent reply	other threads:[~2010-09-15  8:29 UTC|newest]

Thread overview: 20+ 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  5:29       ` Huang Ying
2010-09-15  7:51       ` Martin Schwidefsky
2010-09-15  8:28       ` Peter Zijlstra [this message]
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
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
  -- strict thread matches above, loose matches on Subject: below --
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=1284539320.3764.266.camel@twins \
    --to=peterz@infradead.org \
    --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=rmk@arm.linux.org.uk \
    --cc=schwidefsky@de.ibm.com \
    --cc=ying.huang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.