From: David Ford <david+cert@blue-labs.org>
To: Greg KH <greg@kroah.com>
Cc: Thunder from the hill <thunder@ngforever.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.19-pre10-ac2, compile warnings/failures
Date: Tue, 11 Jun 2002 10:15:30 -0400 [thread overview]
Message-ID: <3D060602.20409@blue-labs.org> (raw)
In-Reply-To: <3D0518BF.4090404@blue-labs.org> <Pine.LNX.4.44.0206101855290.17269-100000@hawkeye.luckynet.adm> <20020611060353.GA6711@kroah.com>
It's been brought up over and over the last couple of years. GCC
started warning about it quite a while ago and it's been named as a bad
form. Patches to fix various things have been submitted sporadically
for a long time as well. Future versions of GCC will mark it as an error.
David
Greg KH wrote:
>On Mon, Jun 10, 2002 at 06:59:36PM -0600, Thunder from the hill wrote:
>
>
>>Hi,
>>
>>On Mon, 10 Jun 2002, David Ford wrote:
>>
>>
>>>People, please don't do things like:
>>>
>>>[bad use of doublequotes]
>>>
>>>Patches keep going in to fix this.
>>>
>>>[good use of doublequotes]
>>>
>>>
>>The same applies to 2.5. Can someone write a perl script that treats it so
>>anonymous that it can find these buggy places?
>>
>>
>
>And could someone actually _tell_ the maintainers of these drivers that
>there is a problem? And what compiler version causes it?
>
>This the first I've heard of this problem.
>
>greg k-h
>
>
next prev parent reply other threads:[~2002-06-11 14:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-10 21:23 2.4.19-pre10-ac2, compile warnings/failures David Ford
2002-06-11 0:59 ` Thunder from the hill
2002-06-11 6:03 ` Greg KH
2002-06-11 14:15 ` David Ford [this message]
[not found] <Pine.LNX.4.21.0206101811180.364-100000@inbetween.blorf.net>
2002-06-11 1:22 ` Thunder from the hill
2002-06-11 3:05 ` David Ford
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=3D060602.20409@blue-labs.org \
--to=david+cert@blue-labs.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thunder@ngforever.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