From: Dmitry Torokhov <dmitry.torokhov@gmail•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, Henrik Rydberg <rydberg@euromail•se>
Subject: Re: linux-next: input tree build failure
Date: Mon, 9 Mar 2009 22:02:51 -0700 [thread overview]
Message-ID: <20090310050250.GB18546@dtor-d630.eng.vmware.com> (raw)
In-Reply-To: <20090310154919.31f45de6.sfr@canb.auug.org.au>
Hi Stephen,
On Tue, Mar 10, 2009 at 03:49:19PM +1100, Stephen Rothwell wrote:
> Hi Dmitry,
>
> Today's linux-next build (x86_64 allmodconfig) failed like this:
>
> drivers/input/mouse/bcm5974.c: In function 'report_tp_state':
> drivers/input/mouse/bcm5974.c:301: error: 'raw_n' undeclared (first use in this function)
> drivers/input/mouse/bcm5974.c:341: error: 'ibt' undeclared (first use in this function)
>
> Caused by commit d86c56b75718295025be895a0f7a157298c84491 ("Input:
> bcm5974 - augment debug information").
>
> I have merged the version of the input tree from next-20090306 instead of
> today's.
I just noticed the failure and rebuilt the tree without that patch as
it was dependent upon another bcm change. Sorry about that.
--
Dmitry
next prev parent reply other threads:[~2009-03-10 5:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 4:49 linux-next: input tree build failure Stephen Rothwell
2009-03-10 5:02 ` Dmitry Torokhov [this message]
2009-03-10 5:14 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2010-01-25 5:52 Stephen Rothwell
2010-01-25 6:46 ` Dmitry Torokhov
2010-01-25 7:26 ` Tobias Klauser
2009-12-07 9:03 Stephen Rothwell
2009-12-07 16:25 ` Randy Dunlap
2009-12-07 17:36 ` Dmitry Torokhov
2009-12-07 22:16 ` Stephen Rothwell
2008-08-19 6:31 Stephen Rothwell
2008-08-19 13:01 ` Dmitry Torokhov
2008-08-19 19:59 ` Greg KH
2008-08-19 20:00 ` Greg KH
2008-08-20 5:49 ` Stephen Rothwell
2008-08-20 18:35 ` Greg KH
2008-08-22 20:29 ` Dmitry Torokhov
2008-08-22 22:15 ` Alfred E. Heggestad
2008-08-25 0:01 ` 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=20090310050250.GB18546@dtor-d630.eng.vmware.com \
--to=dmitry.torokhov@gmail$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rydberg@euromail$(echo .)se \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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