From: Thayne Harbaugh <thayne@realmsys.com>
To: Dave Peterson <dsp@llnl.gov>
Cc: Andrew Morton <akpm@osdl.org>,
alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org,
bluesmoke-devel@lists.sourceforge.net, zhenyu.z.wang@intel.com
Subject: Re: [PATCH 7/15] EDAC: i82875p cleanup
Date: Fri, 03 Mar 2006 18:43:28 -0700 [thread overview]
Message-ID: <1141436608.14012.23.camel@localhost.localdomain> (raw)
In-Reply-To: <200603031047.01445.dsp@llnl.gov>
On Fri, 2006-03-03 at 10:47 -0800, Dave Peterson wrote:
> On Thursday 02 March 2006 18:30, Andrew Morton wrote:
> > Dave Peterson <dsp@llnl.gov> wrote:
> > > +#ifdef CORRECT_BIOS
> > > +fail0:
> > > +#endif
> >
> > What is CORRECT_BIOS? Is the fact that it's never defined some sort of
> > commentary? ;)
>
> I'm not sure about this. I'm cc'ing Thayne Harbaugh and Wang Zhenyu since
> their names are in the credits for the i82875p module. Maybe they can
> provide some info.
This is something that is my style - I don't care for "#if 0" or "#if
1". I usually drop a "#undef COMMENT_TAG" someplace with a "/* ... */"
comment next to it so that it's not some unknown tag.
I haven't looked through the code yet so I can't remember if it's
something I left and if it is, what it does.
I just looked, and I don't recognize it - "cvs annotate" lists it ass
being last touched by dsp_llnl ;^).
--
A silly version!
so I fix the stripping beat
with bitter sleep snot.
next prev parent reply other threads:[~2006-03-04 1:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 1:48 Dave Peterson
2006-03-03 2:30 ` Andrew Morton
2006-03-03 18:47 ` Dave Peterson
2006-03-04 1:43 ` Thayne Harbaugh [this message]
2006-03-04 17:06 ` Henrique de Moraes Holschuh
2006-03-07 5:06 ` Wang Zhenyu
2006-03-07 15:47 ` Henrique de Moraes Holschuh
2006-03-03 2:30 ` 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=1141436608.14012.23.camel@localhost.localdomain \
--to=thayne@realmsys.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bluesmoke-devel@lists.sourceforge.net \
--cc=dsp@llnl.gov \
--cc=linux-kernel@vger.kernel.org \
--cc=zhenyu.z.wang@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
Powered by JetHome