linux-kernel - Re: linux-next: build failure after merge of the v4l-dvb tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 03 May 2010 04:58:30 -0300
From:	Mauro Carvalho Chehab <mchehab@...radead.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
CC:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: build failure after merge of the v4l-dvb tree

Stephen Rothwell wrote:
> Hi Mauro,
> 
> On Wed, 28 Apr 2010 11:07:10 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>> On Mon, 12 Apr 2010 12:40:41 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>>> After merging the v4l-dvb tree, today's linux-next build (powerpc
>>> ppc64_defconfig) failed like this:
>>>
>>> drivers/input/input.c: In function 'input_default_setkeycode':
>>> drivers/input/input.c:691: error: 'keycode' undeclared (first use in this function)
>>>
>>> Caused by commit df7ad46fc171965103f02649f6c2f02c6ca8b331 ("Merge branch
>>> 'master' of /home/v4l/bare_trees/v4l-dvb").  The merge resolution is not
>>> quite right.
>>>
>>> I have used the v4l-dvb tree from next-20100409 for today.
>> I am still getting this build failure ...
> 
> Any chance of it being fixed?

Done. 


-- 

Cheers,
Mauro
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/