From: Adrian Bunk <bunk@stusta.de>
To: Daniel Walker <dwalker@mvista.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] mtd redboot (also gcc 4.1 warning fix)
Date: Wed, 10 May 2006 07:37:01 +0200 [thread overview]
Message-ID: <20060510053701.GO3570@stusta.de> (raw)
In-Reply-To: <200605100256.k4A2u4FO031737@dwalker1.mvista.com>
On Tue, May 09, 2006 at 07:56:04PM -0700, Daniel Walker wrote:
> unsigned long may not always be 32 bits, right ? This patch fixes the
> warning, but not the bug .
>...
IOW, all your patch does is to hide a bug?
Not exactly an improvement...
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-05-10 5:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 2:56 [BUG] mtd redboot (also gcc 4.1 warning fix) Daniel Walker
2006-05-10 3:14 ` Matheus Izvekov
2006-05-10 3:20 ` Daniel Walker
2006-05-10 3:29 ` Olof Johansson
2006-05-10 3:31 ` Daniel Walker
2006-05-10 4:54 ` Matheus Izvekov
2006-05-10 9:04 ` Steven Rostedt
2006-05-10 5:37 ` Adrian Bunk [this message]
2006-05-10 9:00 ` Steven Rostedt
2006-05-10 14:43 ` Daniel Walker
2006-05-10 14:35 ` Daniel Walker
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=20060510053701.GO3570@stusta.de \
--to=bunk@stusta.de \
--cc=dwalker@mvista.com \
--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