From: Christoph Hellwig <hch@infradead.org>
To: William Lee Irwin III <wli@holomorphy.com>,
Ingo Molnar <mingo@elte.hu>,
Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, Scott Wood <scott@timesys.com>
Subject: Re: [patch] generic-hardirqs.patch, 2.6.9-rc1-bk14
Date: Wed, 8 Sep 2004 14:01:46 +0100 [thread overview]
Message-ID: <20040908140146.A31601@infradead.org> (raw)
In-Reply-To: <20040908125755.GC3106@holomorphy.com>; from wli@holomorphy.com on Wed, Sep 08, 2004 at 05:57:55AM -0700
On Wed, Sep 08, 2004 at 05:57:55AM -0700, William Lee Irwin III wrote:
> * Christoph Hellwig <hch@infradead.org> wrote:
> >> And make hardirq.o dependent on some symbols the architectures set.
> >> Else arches that don't use it carry tons of useless baggage around
> >> (and in fact I'm pretty sure it wouldn't even compie for many)
>
> On Wed, Sep 08, 2004 at 02:45:47PM +0200, Ingo Molnar wrote:
> > it compiles fine on x86, x64, ppc and ppc64. Why do you think it wont
> > compile on others?
> > wrt. unused generic functions - why dont we drop them link-time?
>
> It may be time for a __weak define to abbreviate __attribute__((weak));
> we seem to use it in enough places.
Personally I'm extremly unhappy with that week model for things like
this. There's no reason why architectures could implement irq handling
as inlines. Or in case of s390 not at all.
next prev parent reply other threads:[~2004-09-08 13:09 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 12:06 [patch] generic-hardirqs.patch, 2.6.9-rc1-bk14 Ingo Molnar
2004-09-08 12:29 ` La Monte H.P. Yarroll
2004-09-08 13:25 ` Christoph Hellwig
2004-09-08 13:40 ` Ingo Molnar
2004-09-08 13:47 ` Christoph Hellwig
2004-09-08 12:34 ` Christoph Hellwig
2004-09-08 12:45 ` Ingo Molnar
2004-09-08 12:49 ` Christoph Hellwig
2004-09-08 13:05 ` Ingo Molnar
2004-09-08 13:12 ` Christoph Hellwig
2004-09-08 13:17 ` Ingo Molnar
2004-09-08 13:20 ` Christoph Hellwig
2004-09-08 13:32 ` Ingo Molnar
2004-09-09 17:56 ` Scott Wood
2004-09-08 12:57 ` William Lee Irwin III
2004-09-08 13:01 ` Christoph Hellwig [this message]
2004-09-08 13:09 ` William Lee Irwin III
2004-09-08 13:10 ` Ingo Molnar
2004-09-08 13:34 ` Zwane Mwaikambo
2004-09-08 13:31 ` Christoph Hellwig
2004-09-08 13:47 ` Zwane Mwaikambo
2004-09-08 14:09 ` Arjan van de Ven
2004-09-08 18:25 ` Ingo Molnar
2004-09-08 18:42 ` Zwane Mwaikambo
2004-09-08 21:14 ` [patch] generic-hardirqs-2.6.9-rc1-mm4.patch Ingo Molnar
2004-09-09 16:57 ` Christoph Hellwig
2004-09-09 17:24 ` Ingo Molnar
2004-09-09 17:53 ` William Lee Irwin III
2004-09-09 17:54 ` Arjan van de Ven
2004-09-09 17:56 ` William Lee Irwin III
2004-09-09 20:10 ` Russell King
2004-09-09 20:51 ` Scott Wood
2004-09-09 21:00 ` Russell King
2004-09-10 5:57 ` Arjan van de Ven
2004-09-09 20:24 ` Rafael J. Wysocki
2004-09-09 20:40 ` Andrew Morton
2004-09-09 20:49 ` Ingo Molnar
2004-09-08 13:03 ` [patch] generic-hardirqs.patch, 2.6.9-rc1-bk14 Arjan van de Ven
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=20040908140146.A31601@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=scott@timesys.com \
--cc=wli@holomorphy.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