All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Schlichter <thomas.schlichter@web.de>
To: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix warning about duplicate 'const'
Date: Tue, 9 Mar 2004 02:17:37 +0100	[thread overview]
Message-ID: <200403090217.40867.thomas.schlichter@web.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0403081627450.9575@ppc970.osdl.org>

Am Dienstag, 9. März 2004 01:32 schrieb Linus Torvalds:

~~ snip ~~

> 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.

OK, I tested it and gcc 3.3.1 does not complain about this. So with my patch, 
the duplicate 'const' warning goes away here and no other warning occours...

But I don't know how other versions of gcc behave...

   Thomas


  reply	other threads:[~2004-03-09  1:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-08 23:43 [PATCH] fix warning about duplicate 'const' Thomas Schlichter
2004-03-09  0:14 ` Andrew Morton
2004-03-09  0:32   ` Linus Torvalds
2004-03-09  1:17     ` Thomas Schlichter [this message]
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=200403090217.40867.thomas.schlichter@web.de \
    --to=thomas.schlichter@web.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.