From: Adrian Bunk <bunk@fs.tum.de>
To: Andrew Morton <akpm@osdl.org>, jgarzik@pobox.com, linux@syskonnect.de
Cc: linux-kernel@vger.kernel.org
Subject: 2.6.1-rc1-mm2: warning in drivers/net/sk98lin/skge.c
Date: Tue, 6 Jan 2004 19:13:18 +0100 [thread overview]
Message-ID: <20040106181318.GH11523@fs.tum.de> (raw)
In-Reply-To: <20040105002056.43f423b1.akpm@osdl.org>
On Mon, Jan 05, 2004 at 12:20:56AM -0800, Andrew Morton wrote:
>...
> All 253 patches
>...
> 2.6.0-rc1-netdrvr-exp1.patch
>...
I got the following compile warning:
<-- snip -->
...
CC drivers/net/sk98lin/skge.o
drivers/net/sk98lin/skge.c: In function `skge_probe':
drivers/net/sk98lin/skge.c:713: warning: unused variable `proc_root_initialized'
...
<-- snip -->
2.6.0-rc1-netdrvr-exp1.patch contains
--- 25/drivers/net/sk98lin/skge.c~2.6.0-rc1-netdrvr-exp1 2004-01-03 14:07:17.000000000 -0800
+++ 25-akpm/drivers/net/sk98lin/skge.c 2004-01-03 14:07:18.000000000 -0800
...
#ifdef CONFIG_PROC_FS
+ int proc_root_initialized = 0;
struct proc_dir_entry *pProcFile;
#endif
...
but no other occurence of proc_root_initialized where it would be used.
Is this some kind of merge error?
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2004-01-06 18:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 8:20 2.6.1-rc1-mm2 Andrew Morton
2004-01-05 9:15 ` 2.6.1-rc1-mm2 Dax Kelson
2004-01-05 9:10 ` 2.6.1-rc1-mm2 Andrew Morton
2004-01-05 17:04 ` 2.6.1-rc1-mm2 Matthias Urlichs
2004-01-05 22:45 ` 2.6.1-rc1-mm2 (compile stats) John Cherry
2004-01-06 18:13 ` Adrian Bunk [this message]
2004-01-06 18:20 ` 2.6.1-rc1-mm2: warning in drivers/net/sk98lin/skge.c Andrew Morton
2004-02-08 13:14 ` Adrian Bunk
2004-02-19 0:09 ` Jeff Garzik
2004-01-07 15:40 ` 2.6.1-rc1-mm2: no help text for E100_NAPI Adrian Bunk
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=20040106181318.GH11523@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@syskonnect.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