From: Sachin Sant <sachinp@in.ibm.com>
To: netdev <netdev@vger.kernel.org>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
linux-s390@vger.kernel.org, ursula.braun@de.ibm.com,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: [-next Oct 13] Build failure drivers/s390/net/ctcm_mpc.o
Date: Wed, 13 Oct 2010 20:39:16 +0530 [thread overview]
Message-ID: <4CB5CB9C.9030603@in.ibm.com> (raw)
Today's next fails to build on a s390 box with following
error
drivers/s390/net/ctcm_mpc.c: In function ctc_mpc_dealloc_ch:
drivers/s390/net/ctcm_mpc.c:541: error: struct net_device has no member named refcnt
The code in question was changed by
commit 29b4433d991c88d86ca48a4c1cc33c671475be4b
net: percpu net_device refcount
The net_device struct member refcnt was changed from atomic_t to
int __percpu.
Thanks
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
next reply other threads:[~2010-10-13 15:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 15:09 Sachin Sant [this message]
2010-10-13 16:12 ` [-next Oct 13] Build failure drivers/s390/net/ctcm_mpc.o David Miller
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=4CB5CB9C.9030603@in.ibm.com \
--to=sachinp@in.ibm.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-next@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ursula.braun@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.