From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-s390@vger.kernel.org, heiko.carstens@de.ibm.com
Subject: Re: [BUILD-FAILURE] next-20081217-s390x-'struct device' has no member named 'knode_parent'
Date: Thu, 18 Dec 2008 10:47:45 +0100 [thread overview]
Message-ID: <1229593665.7086.1.camel@localhost> (raw)
In-Reply-To: <20081217181745.GA18420@linux.vnet.ibm.com>
On Wed, 2008-12-17 at 23:47 +0530, Kamalesh Babulal wrote:
> drivers/s390/cio/device.c: In function 'io_subchannel_register':
> drivers/s390/cio/device.c:913: error: 'struct device' has no member
> named 'knode_parent'
> make[2]: *** [drivers/s390/cio/device.o] Error 1
> make[1]: *** [drivers/s390/cio] Error 2
> make: *** [drivers/s390] Error 2
Should be fixed now by the following patch from Cornelia:
commit efe46b59567ae999ff7d344170d21f093159ad80
Author: Cornelia Huck <cornelia.huck@de.ibm.com>
Date: Thu Dec 18 10:26:55 2008 +0100
[S390] cio: Use device_is_registered().
Check if a ccw device is registered via device_is_registered()
and not via the old kludge of checking the membership in driver
core internal klists.
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
You'll find the fix in the features branch of git390 which will be
included in the next linux-next kernel.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
next prev parent reply other threads:[~2008-12-18 9:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 12:25 linux-next: Tree for December 17 Stephen Rothwell
2008-12-17 18:17 ` [BUILD-FAILURE] next-20081217-s390x-'struct device' has no member named 'knode_parent' Kamalesh Babulal
2008-12-18 9:47 ` Martin Schwidefsky [this message]
2008-12-18 17:17 ` Kamalesh Babulal
2008-12-18 0:13 ` linux-next: Tree for December 17 (DVB) Randy Dunlap
2008-12-18 17:19 ` Randy Dunlap
2008-12-18 0:14 ` linux-next: Tree for December 17 (Radeon DRM BUG) Kevin Winchester
2008-12-18 6:47 ` Dave Airlie
2008-12-18 19:00 ` Bartlomiej Zolnierkiewicz
2008-12-18 20:49 ` Dave Airlie
2008-12-18 22:09 ` Bartlomiej Zolnierkiewicz
2008-12-18 23:39 ` Dave Airlie
2008-12-19 19:45 ` Bartlomiej Zolnierkiewicz
2008-12-19 23:07 ` Kevin Winchester
2008-12-20 1:58 ` Kevin Winchester
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=1229593665.7086.1.camel@localhost \
--to=schwidefsky@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.