From: corbet@lwn.net (Jonathan Corbet)
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org
Subject: Re: linux-next: bkl-removal build failure
Date: Mon, 19 May 2008 11:12:45 -0600 [thread overview]
Message-ID: <4642.1211217165@vena.lwn.net> (raw)
In-Reply-To: Your message of "Mon, 19 May 2008 16:32:03 +1000." <20080519163203.89a54b82.sfr@canb.auug.org.au>
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Today's linux-next build (powerpc ppc64_defconfig) failed like this:
>
> drivers/char/viotape.c: In function 'viotap_open':
> /scratch/sfr/next/drivers/char/viotape.c:692: error: expected ';' before 'get_dev_info'
Well, that's embarrassing. There are limits to what can be done with
"make allyesconfig" when you only have one architecture at hand...:)
I've put your fix into my tree, thanks and sorry for the trouble.
jon
next prev parent reply other threads:[~2008-05-19 17:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 6:32 linux-next: bkl-removal build failure Stephen Rothwell
2008-05-19 17:12 ` Jonathan Corbet [this message]
2008-05-20 3:26 ` Stephen Rothwell
2008-05-20 4:43 ` 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=4642.1211217165@vena.lwn.net \
--to=corbet@lwn.net \
--cc=linux-next@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 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).