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,
Ping Cheng <pinglinux@gmail.com>
Subject: Re: linux-next: build failure after merge of the final tree (input tree related)
Date: Tue, 28 Dec 2010 18:34:58 -0800 [thread overview]
Message-ID: <20101229023457.GA4206@core.coreip.homeip.net> (raw)
In-Reply-To: <20101229125129.d48fb6fc.sfr@canb.auug.org.au>
On Wed, Dec 29, 2010 at 12:51:29PM +1100, Stephen Rothwell wrote:
> Hi Dmitry,
>
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> drivers/input/touchscreen/wacom_w8001.c: In function 'w8001_setup':
> drivers/input/touchscreen/wacom_w8001.c:287: error: implicit declaration of function 'mdelay'
>
> Caused by commit b8fe15cb1b435928f9967d660e925fe7afb32787 ("Input:
> wacom_w8001 - support pen or touch only devices"). See Rule 1 in
> Documentation/SubmitChecklist.
>
> I have reverted that commit for today.
Thank you Stephen, I'll fix this up in my tree.
--
Dmitry
next prev parent reply other threads:[~2010-12-29 2:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-29 1:51 linux-next: build failure after merge of the final tree (input tree related) Stephen Rothwell
2010-12-29 2:34 ` Dmitry Torokhov [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2011-09-19 8:46 Stephen Rothwell
2011-09-19 9:01 ` Tobias Klauser
2010-08-20 3:12 Stephen Rothwell
2010-08-21 7:39 ` 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=20101229023457.GA4206@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pinglinux@gmail.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 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).