From: joern@wohnheim.fh-wedel.de (Jörn Engel)
To: linux-mtd@lists.infradead.org
Subject: [PATCH] makefile bug and some cleanup
Date: Sun, 2 Mar 2003 11:57:30 +0100 [thread overview]
Message-ID: <20030302105730.GA18324@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <20030302092359.GN15015@pengutronix.de>
On Sun, 2 March 2003 10:23:59 +0100, Robert Schwebel wrote:
>
> Here are two patches against current CVS; the first one fixes the
> utils/Makefile, the second one removes some warnings for erase.c.
First looks trivial. The second feels wrong.
> - erase.length, erase.start);
> + (unsigned long)erase.length, (unsigned long)erase.start);
People (including me) are easily lured into fixing the warnings, which
are only symptoms, instead of the real causes. And this looks exactly
like a symptom fix.
Could be right, though, I didn't dig into the code yet. Maybe tonight.
J?rn
--
Geld macht nicht gl?cklich.
Gl?ck macht nicht satt.
next prev parent reply other threads:[~2003-03-02 10:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-02 9:23 [PATCH] makefile bug and some cleanup Robert Schwebel
2003-03-02 10:57 ` Jörn Engel [this message]
2003-03-02 18:14 ` Jörn Engel
2003-03-03 10:58 ` Jörn Engel
2003-03-04 8:13 ` Robert Schwebel
2003-03-04 9:12 ` Jörn Engel
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=20030302105730.GA18324@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=linux-mtd@lists.infradead.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