From: Christoph Hellwig <hch@infradead.org>
To: Stewart Smith <stewart@linux.org.au>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Jeff Garzik <jgarzik@pobox.com>,
David Woodhouse <dwmw2@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [EVIL-PATCH] getting rid of lib/lib.a and breaking many archs in the processes (was Re: [PATCH] fixed: CRC32=y && 8193TOO=m unresolved symbols)
Date: Sat, 7 Jun 2003 08:39:29 +0100 [thread overview]
Message-ID: <20030607083929.A19009@infradead.org> (raw)
In-Reply-To: <20030607073321.GC1540@cancer>; from stewart@linux.org.au on Sat, Jun 07, 2003 at 05:33:21PM +1000
On Sat, Jun 07, 2003 at 05:33:21PM +1000, Stewart Smith wrote:
> Is it a good idea to make the archs themselves include the generic implementation if they don't do it themselves? Or is there a way to detect this in the build system (this would be more elegant, but I have no idea how to do it).
You can always add a HAVE_ARCH_FOO #define. Btw, we have so many
of those these days that an <asm/config.h> for them might be a better
choice than polluting random other header. Opinions?
next prev parent reply other threads:[~2003-06-07 7:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-03 1:13 CRC32=y && 8193TOO=m unresolved symbols Stewart Smith
2003-06-03 13:16 ` David Woodhouse
2003-06-04 5:56 ` [PATCH] fixed: " Stewart Smith
2003-06-04 15:28 ` Jeff Garzik
2003-06-04 15:30 ` David Woodhouse
2003-06-04 15:32 ` Jeff Garzik
2003-06-04 15:41 ` Linus Torvalds
2003-06-07 7:33 ` [EVIL-PATCH] getting rid of lib/lib.a and breaking many archs in the processes (was Re: [PATCH] fixed: CRC32=y && 8193TOO=m unresolved symbols) Stewart Smith
2003-06-07 7:39 ` Christoph Hellwig [this message]
2003-06-07 17:34 ` Linus Torvalds
2003-06-07 19:02 ` Sam Ravnborg
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=20030607083929.A19009@infradead.org \
--to=hch@infradead.org \
--cc=dwmw2@infradead.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stewart@linux.org.au \
--cc=torvalds@transmeta.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®