From: Linus Torvalds <torvalds@osdl.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Thomas Schlichter <thomas.schlichter@web.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix warning about duplicate 'const'
Date: Mon, 8 Mar 2004 16:32:06 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.58.0403081627450.9575@ppc970.osdl.org> (raw)
In-Reply-To: <20040308161410.49127bdf.akpm@osdl.org>
On Mon, 8 Mar 2004, Andrew Morton wrote:
> >
> > This is done by removing the 'const' from the temporary variables of the min()
> > and max() macros. For me it seems to have no negative impact, so please
> > consider applying...
>
> I think there was a reason for those consts in kernel.h's min() and max()
> macros, but memory fails me. Linus, do you recall?
I'm not 100% sure, but I think they are required to make a few other
warnings go away. The fact that gcc complains about "const typeof" is a
gcc misfeature, I think, and should be fixed there.
The warnings the extra "const" fixes is something like:
int a;
const int b;
min(a,b)
where otherwise it would complain about pointers to different types when
comparing the type of the pointer. Or something.
Linus
next prev parent reply other threads:[~2004-03-09 0:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-08 23:43 Thomas Schlichter
2004-03-09 0:14 ` Andrew Morton
2004-03-09 0:32 ` Linus Torvalds [this message]
2004-03-09 1:17 ` Thomas Schlichter
2004-03-09 1:32 ` Linus Torvalds
2004-03-09 1:35 ` Linus Torvalds
2004-03-10 4:08 ` Keith Duthie
[not found] ` <20040310054918.GB4068@twiddle.net>
2004-03-10 8:10 ` Gabriel Dos Reis
[not found] ` <20040310064001.GA7584@daikokuya.co.uk>
2004-03-10 10:15 ` Joseph S. Myers
2004-03-10 15:43 ` Linus Torvalds
2004-03-10 18:22 ` Richard Henderson
2004-03-10 18:29 ` Andrew Haley
2004-03-10 18:35 ` Paul Koning
2004-03-10 18:37 ` Richard Henderson
2004-03-16 1:46 ` Mike Stump
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=Pine.LNX.4.58.0403081627450.9575@ppc970.osdl.org \
--to=torvalds@osdl.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.schlichter@web.de \
/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®