From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Greg KH <greg@kroah.com>
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
linux-next@vger.kernel.org,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: linux-next: s390 build failure
Date: Fri, 20 Jun 2008 13:52:57 +1000 [thread overview]
Message-ID: <20080620135257.102f024c.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 658 bytes --]
Hi Greg, Cornelia,
Yesterday's (and back to next-20080612) linux-next build (s390
allnoconfig (and others) with an s390s compiler) fails with this error:
drivers/s390/cio/cio.c:573: error: 'struct device' has no member named 'init_name'
Bisecting lead to the commit "s390: bus_id -> dev_set_name() changes" in
the driver-core tree. I suspect this was caused by the removal of
"driver core: add init_name to struct device" from the driver-core tree
on June 11 (even though the former patch was earlier in the series then
the latter).
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2008-06-20 3:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 3:52 Stephen Rothwell [this message]
2008-06-20 7:58 ` linux-next: s390 build failure Cornelia Huck
2008-06-23 15:22 ` Cornelia Huck
2008-06-23 15:23 ` [PATCH] s390: bus_id -> dev_set_name() changes Cornelia Huck
2008-06-23 15:24 ` [PATCH] s390: bus_id -> dev_set_name() for css and ccw busses Cornelia Huck
2008-06-23 22:13 ` linux-next: s390 build failure Greg KH
-- strict thread matches above, loose matches on Subject: below --
2009-03-19 23:53 Stephen Rothwell
2009-03-19 23:42 Stephen Rothwell
2009-03-20 8:24 ` Heiko Carstens
2009-03-20 10:00 ` Ingo Molnar
2009-03-20 10:33 ` Heiko Carstens
2008-06-20 2:42 Stephen Rothwell
2008-06-20 11:42 ` Jens Axboe
2008-06-21 8:07 ` Heiko Carstens
2008-06-26 9:14 ` Jens Axboe
2008-06-20 11:51 ` Martin Schwidefsky
2008-05-12 8:03 Stephen Rothwell
2008-05-12 16:49 ` Greg KH
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=20080620135257.102f024c.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=cornelia.huck@de.ibm.com \
--cc=greg@kroah.com \
--cc=linux-next@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).