From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Jason Wessel <jason.wessel@windriver.com>,
Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: linux-next: build failure after merge of the final tree (input tree related)
Date: Sat, 21 Aug 2010 00:39:27 -0700 [thread overview]
Message-ID: <20100821073927.GA2160@core.coreip.homeip.net> (raw)
In-Reply-To: <20100820131224.02f7cb9f.sfr@canb.auug.org.au>
Hi Stephen,
On Fri, Aug 20, 2010 at 01:12:24PM +1000, Stephen Rothwell wrote:
> Hi Dmitry,
>
> After merging the final tree, today's linux-next build (i386 defconfig)
> failed like this:
>
> In file included from drivers/gpu/drm/i915/i915_irq.c:29:
> include/linux/sysrq.h:45: error: expected declaration specifiers or '...' before 'bool'
>
> Caused by commit a821bafce37b26499e2bfbf2e6b96b0636efc014 ("Input: sysrq
> - drop tty argument form handle_sysrq()") from the input tree which
> (despite not mentioning this) changed an "int" argument to "bool" but
> neglected to include linux/types.h.
>
> I added this patch for today:
Thank you very much for the patch. I folded it into original patch to
avoid build failures in case someone needs to bisect.
--
Dmitry
next prev parent reply other threads:[~2010-08-21 7:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-20 3:12 linux-next: build failure after merge of the final tree (input tree related) Stephen Rothwell
2010-08-21 7:39 ` Dmitry Torokhov [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-09-19 8:46 Stephen Rothwell
2011-09-19 9:01 ` Tobias Klauser
2010-12-29 1:51 Stephen Rothwell
2010-12-29 2:34 ` Dmitry Torokhov
2010-12-29 23:51 ` Stephen Rothwell
2010-12-30 18:06 ` Ping Cheng
2010-12-30 19:58 ` Geert Uytterhoeven
2010-12-30 20:10 ` Ping Cheng
2011-01-02 8:05 ` Dmitry Torokhov
2010-03-23 6:54 Stephen Rothwell
2010-03-23 7:31 ` Dmitry Torokhov
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=20100821073927.GA2160@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@suse.de \
--cc=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--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).