From: Randy Dunlap <randy.dunlap@oracle.com>
To: Bela Lubkin <blubkin@vmware.com>
Cc: Andrew Morton <akpm@osdl.org>, Corey Minyard <minyard@acm.org>,
OpenIPMI Developers <openipmi-developer@lists.sourceforge.net>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Joseph Barnett <jbarnett@motorola.com>
Subject: Re: [Openipmi-developer] [PATCH 9/12] IPMI: add pigeonpoint poweroff
Date: Sun, 03 Dec 2006 20:01:56 -0800 [thread overview]
Message-ID: <45739DB4.6000806@oracle.com> (raw)
In-Reply-To: <FE74AC4E0A23124DA52B99F17F44159701DBC05B@PA-EXCH03.vmware.com>
Bela Lubkin wrote:
> Andrew Morton wrote:
>
>>> Sometime, please go through the IPMI code looking for all these
>>> statically-allocated things which are initialised to 0 or NULL and remove
>>> all those intialisations? They're unneeded, they increase the vmlinux
>>> image size and there are quite a number of them. Thanks.
>
> Randy Dunlop replied:
>
>> I was just about to send that patch. Here it is,
>> on top of the series-of-12.
> ...
>> -static int bt_debug = BT_DEBUG_OFF;
>> +static int bt_debug;
>
> Is it wise to significantly degrade code readability to work around a minor
> compiler / linker bug?
Is that the only one that is a problem?
I don't think it's a problem. We *know* that static data areas
are init to 0. Everything depends on that. If that didn't work
it would all break.
I could say that it's a nice coincidence that BT_DEBUG_OFF == 0,
but I think that it's more than coincidence.
--
~Randy
next prev parent reply other threads:[~2006-12-04 4:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 4:37 Corey Minyard
2006-12-03 21:26 ` Andrew Morton
2006-12-04 2:35 ` Corey Minyard
2006-12-04 2:54 ` Randy Dunlap
2006-12-04 3:53 ` [Openipmi-developer] " Bela Lubkin
2006-12-04 4:01 ` Randy Dunlap [this message]
2006-12-04 4:12 ` Randy Dunlap
2006-12-05 14:01 ` Corey Minyard
2006-12-05 16:19 ` Bela Lubkin
2006-12-04 4:21 ` Bela Lubkin
2006-12-04 12:06 ` Horst H. von Brand
2006-12-04 3:00 ` Randy Dunlap
2006-12-04 5:03 ` Andrew Morton
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=45739DB4.6000806@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@osdl.org \
--cc=blubkin@vmware.com \
--cc=jbarnett@motorola.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=openipmi-developer@lists.sourceforge.net \
/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®