linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: "Kevin B. Hendricks" <kevin.hendricks@sympatico.ca>
Cc: Franz Sirl <Franz.Sirl-ppc@lauterbach.com>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: can/should we use gcc 3.1 to compile kernels
Date: Fri, 7 Jun 2002 16:59:53 -0700	[thread overview]
Message-ID: <20020607235953.GR14252@opus.bloom.county> (raw)
In-Reply-To: <200206071939.44925.kevin.hendricks@sympatico.ca>


On Fri, Jun 07, 2002 at 07:39:44PM -0400, Kevin B. Hendricks wrote:
> Hi,
>
> FYI: I counted 1175 occurences of warnings like the following:
>
> inode.c:2462: warning: concatenation of string literals with __FUNCTION__
> is deprecated
>
> So I hope someone has a nice sed or awk script to fix all of these in some
> automatic way.

There are/were rumblings of doing some standard debug macros for 2.5,
so...

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-06-07 23:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-08 17:41 can/should we use gcc 3.1 to compile kernels Kevin B. Hendricks
2002-06-07 18:31 ` Kaoru Fukui
2002-06-07 19:38 ` Tom Rini
2002-06-07 19:44   ` Kevin B. Hendricks
2002-06-07 20:19     ` Tom Rini
2002-06-07 20:36       ` Franz Sirl
2002-06-07 20:45         ` Tom Rini
2002-06-07 20:58           ` Franz Sirl
2002-06-07 23:39             ` Kevin B. Hendricks
2002-06-07 23:59               ` Tom Rini [this message]
2002-06-07 20:44       ` Kevin B. Hendricks
2002-06-07 20:50         ` Franz Sirl
2002-06-07 21:06           ` Kevin B. Hendricks
2002-06-07 21:40           ` Kaoru Fukui
2002-06-07 21:11 ` More GCC 3.1 Qs Conn Clark

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=20020607235953.GR14252@opus.bloom.county \
    --to=trini@kernel.crashing.org \
    --cc=Franz.Sirl-ppc@lauterbach.com \
    --cc=kevin.hendricks@sympatico.ca \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).