From: "Andi Kleen" <andi@firstfloor.org>
To: "Peter Zijlstra" <peterz@infradead.org>
Cc: "Huang Ying" <ying.huang@intel.com>,
"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>
Subject: Re: [PATCH -tip -v4] irq_work: generic hard-irq context callbacks
Date: Wed, 15 Sep 2010 17:10:03 +0200 (CEST) [thread overview]
Message-ID: <37141.91.60.150.116.1284563403.squirrel@www.firstfloor.org> (raw)
> 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.
I don't think it's a reasonable requirement to have every contributor
compile on all architectures. If that was a general requirement
soon nobody would send patches anymore.
Cross arch breakages happen rarely and can be usually repaired after
the fact.
-Andi
next reply other threads:[~2010-09-15 15:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 15:10 Andi Kleen [this message]
2010-09-15 15:41 ` Peter Zijlstra
2010-09-15 19:30 ` Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2010-09-13 6:50 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
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
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=37141.91.60.150.116.1284563403.squirrel@www.firstfloor.org \
--to=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 \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®