From: Maneesh Soni <maneesh@in.ibm.com>
To: schwidefsky@de.ibm.com
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: s390 drivers compilation
Date: Mon, 1 Nov 2004 15:43:45 -0600 [thread overview]
Message-ID: <20041101214345.GC2613@in.ibm.com> (raw)
Hi Martin,
I get this on 2.6.10-rc1-bk11.
CC [M] drivers/s390/net/netiucv.o
CC [M] drivers/s390/net/fsm.o
CC [M] drivers/s390/net/smsgiucv.o
CC [M] drivers/s390/net/ctcmain.o
drivers/s390/net/ctcmain.c: In function `ch_action_setmode':
drivers/s390/net/ctcmain.c:1221: warning: `saveflags' might be used uninitialized in this function
drivers/s390/net/ctcmain.c: In function `ch_action_restart':
drivers/s390/net/ctcmain.c:1497: warning: `saveflags' might be used uninitialized in this function
drivers/s390/net/ctcmain.c: In function `ch_action_txretry':
drivers/s390/net/ctcmain.c:1648: warning: `saveflags' might be used uninitialized in this function
drivers/s390/net/ctcmain.c: In function `ch_action_haltio':
drivers/s390/net/ctcmain.c:1331: warning: `saveflags' might be used uninitialized in this function
CC [M] drivers/s390/net/ctctty.o
CC [M] drivers/s390/net/ctcdbug.o
CC [M] drivers/s390/net/qeth_main.o
drivers/s390/net/qeth_main.c: In function `qeth_ipv6_generate_eui64':
drivers/s390/net/qeth_main.c:5015: error: structure has no member named `dev_id'
drivers/s390/net/qeth_main.c:5016: error: structure has no member named `dev_id'
drivers/s390/net/qeth_main.c: In function `qeth_netdev_init':
drivers/s390/net/qeth_main.c:5568: error: structure has no member named `dev_id'
drivers/s390/net/qeth_main.c:5570: error: structure has no member named `generate_eui64'
make[2]: *** [drivers/s390/net/qeth_main.o] Error 1
make[1]: *** [drivers/s390/net] Error 2
make: *** [drivers/s390] Error 2
Looks like struct netdevice is missing dev_id and generate_eui64 fields in include/linux/netdevice.h.
Thanks
Maneesh
--
Maneesh Soni
Linux Technology Center,
IBM Austin
email: maneesh@in.ibm.com
Phone: 1-512-838-1896 Fax:
T/L : 6781896
reply other threads:[~2004-11-02 3:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20041101214345.GC2613@in.ibm.com \
--to=maneesh@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.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 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.