From: Danny Cox <Danny.Cox@ECWeb.com>
To: Chris Wedgwood <cw@f00f.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Trivial Comment Patch: 2.6.6-mm3
Date: Wed, 19 May 2004 07:18:14 -0400 [thread overview]
Message-ID: <1084965494.17460.60.camel@vom> (raw)
In-Reply-To: <20040518200742.GA20835@taniwha.stupidest.org>
Chris,
On Tue, 2004-05-18 at 16:07, Chris Wedgwood wrote:
> On Tue, May 18, 2004 at 09:08:57AM -0400, Danny Cox wrote:
>
> > This fixes a comment in the stack overflow check that's wrong with
> > 4K stacks.
>
> > #ifdef CONFIG_DEBUG_STACKOVERFLOW
> > - /* Debugging check for stack overflow: is there less than 1KB free? */
> > + /* Debugging check for stack overflow: is there less than 512B free? */
> > {
> > long esp;
>
> akpm, how about just yank the line? the comment's sanity depends on a
> CONFIG option and also a value in another file from a far off land.
IMHO, I'd say keep the line, but remove the offensive part (everything
past the ':', inclusive).
--
Daniel S. Cox
Electronic Commerce Systems
prev parent reply other threads:[~2004-05-19 11:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 13:08 Trivial Comment Patch: 2.6.6-mm3 Danny Cox
2004-05-18 20:07 ` Chris Wedgwood
2004-05-19 11:18 ` Danny Cox [this message]
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=1084965494.17460.60.camel@vom \
--to=danny.cox@ecweb.com \
--cc=cw@f00f.org \
--cc=linux-kernel@vger.kernel.org \
/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