linux-kernel - Re: linux-next: build failure after merge of the chrome-platform 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 for Android: free password hash cracker in your pocket

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

Date:	Thu, 8 Oct 2015 16:43:55 -0700
From:	Olof Johansson <olof@...om.net>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Emilio López <emilio.lopez@...labora.co.uk>,
	Javier Martinez Canillas <javier@....samsung.com>
Subject: Re: linux-next: build failure after merge of the chrome-platform tree

Stephen,

On Wed, Oct 7, 2015 at 7:34 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi Olof,
>
> After merging the chrome-platform tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> drivers/platform/chrome/cros_ec_vbc.c:136:2: error: unknown field 'is_bin_visible' specified in initializer
>   .is_bin_visible = cros_ec_vbc_is_visible,
>   ^
>
> Caused by commit
>
>   01e7e432df74 ("platform/chrome: Support reading/writing the vboot context")
>
> I have used the chrome-platform tree from next-20151007 for today.

Yeah, sorry about that. I got notified by the 0-day builder but by the
time I had sorted it out you must already have pulled the tree.

Should be fine today.


-Olof
--
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/