From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, Kay Sievers <kay.sievers@vrfy.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: linux-next: s390 build failure
Date: Mon, 12 May 2008 09:49:19 -0700 [thread overview]
Message-ID: <20080512164919.GA7721@kroah.com> (raw)
In-Reply-To: <20080512180335.6a2e8474.sfr@canb.auug.org.au>
On Mon, May 12, 2008 at 06:03:35PM +1000, Stephen Rothwell wrote:
> Hi Greg,
>
> Today's linux-next build (s390 defconfig) fails like this:
>
> drivers/s390/cio/device_fsm.c:53: error: syntax error before ';' token
> drivers/s390/cio/device_fsm.c:54: error: syntax error before ';' token
>
> Caused by commit 67da378c80848bb778ee8caecadcdf17e1e310e0 ("driver-core:
> prepare for removal of 20 char limit from struct device") from the
> driver-core tree. Missing close parentheses on added dev_name() calls.
>
> A touch more care, please.
I have updated version of this in my to-apply queue, I've dropped this
now so linux-next tomorrow should be just fine. I'll add it back in
when I have the cross-build system set up here so that I can test things
to prevent this kind of mess from happening in the future.
Sorry about that.
greg k-h
next prev parent reply other threads:[~2008-05-12 16:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 8:03 linux-next: s390 build failure Stephen Rothwell
2008-05-12 16:49 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
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-06-20 3:52 Stephen Rothwell
2008-06-20 7:58 ` Cornelia Huck
2008-06-23 15:22 ` Cornelia Huck
2008-06-23 22:13 ` Greg KH
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
2009-03-19 23:53 Stephen Rothwell
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=20080512164919.GA7721@kroah.com \
--to=greg@kroah.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-next@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--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.