From: Oleg Drokin <green@namesys.com>
To: John Cherry <cherry@osdl.org>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux v2.5.61
Date: Tue, 18 Feb 2003 15:14:07 +0300 [thread overview]
Message-ID: <20030218151407.A14679@namesys.com> (raw)
In-Reply-To: <1045510507.3406.12.camel@cherrypit.pdx.osdl.net>
Hello!
On Mon, Feb 17, 2003 at 11:35:07AM -0800, John Cherry wrote:
> Warning summary
[...]
> fs/reiserfs: 1 warnings, 0 errors
Note that this warning comes from asm/string.h, when compiling
fs/reiserfs/prints.c
Warning itself is "strchr is defined but not used". It have nothing
to do with reiserfs at all. And I do not see why it is produced at all, since
strchr is declared "static inline".
(BTW, gcc 2.95 does not produces the warning).
Can somebody look at it please?
Bye,
Oleg
next prev parent reply other threads:[~2003-02-18 12:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-15 1:11 Linux v2.5.61 Linus Torvalds
2003-02-15 9:07 ` 2.5.61: tms380tr.c no longer compiles Adrian Bunk
2003-02-15 9:35 ` Jochen Friedrich
2003-02-15 13:53 ` Adrian Bunk
2003-02-15 13:53 ` Linux v2.5.61 Matthias Andree
2003-02-16 1:58 ` Kunihiro Ishiguro
2003-02-16 10:03 ` David Woodhouse
2003-02-17 11:20 ` Erik Hensema
2003-02-15 18:35 ` Christoph Hellwig
2003-02-15 18:45 ` Jeff Garzik
2003-02-15 18:49 ` Christoph Hellwig
2003-02-16 21:32 ` Pavel Machek
2003-02-17 23:56 ` Jeff Garzik
2003-02-17 19:35 ` John Cherry
2003-02-18 0:52 ` Linux v2.5.62 John Cherry
2003-02-18 12:14 ` Oleg Drokin [this message]
2003-02-19 0:43 ` Linux v2.5.61 Bob Miller
[not found] <Pine.LNX.4.44.0302141709410.1376-100000@penguin.transmeta. com>
2003-02-15 2:17 ` Max Krasnyansky
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=20030218151407.A14679@namesys.com \
--to=green@namesys.com \
--cc=cherry@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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