From: Dave Hansen <haveblue@us.ibm.com>
To: Matt Mackall <mpm@selenic.com>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.8-rc2-mm1 link errors
Date: Wed, 28 Jul 2004 19:25:39 -0700 [thread overview]
Message-ID: <1091067939.2871.898.camel@nighthawk> (raw)
In-Reply-To: <20040729021225.GG16310@waste.org>
On Wed, 2004-07-28 at 19:12, Matt Mackall wrote:
> On Wed, Jul 28, 2004 at 07:06:13PM -0700, Dave Hansen wrote:
> > I say, put them back in plain old BSS. Patch attached.
>
> Frankly, I'd rather have the warning if it isn't breaking anything.
I just worry that the warning is indicative of something more insidious
than triggering an error from a symbol checker script.
> Or how about I throw some version conditional magic at it?
I thought about including something in compiler-gcc*, but those files
are still pretty simple at this point, and I hate to add more gunk to
them. It doesn't seem quite worth it to me. But, if that's the way to
go, I can code it up.
-- Dave
next prev parent reply other threads:[~2004-07-29 2:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 23:27 2.6.8-rc2-mm1 link errors Dave Hansen
2004-07-28 23:49 ` Andrew Morton
2004-07-29 0:00 ` Dave Hansen
2004-07-29 2:06 ` Dave Hansen
2004-07-29 2:12 ` Matt Mackall
2004-07-29 2:25 ` Dave Hansen [this message]
2004-07-29 21:07 ` Adrian Bunk
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=1091067939.2871.898.camel@nighthawk \
--to=haveblue@us.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.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