linux-kernel - 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-next>] [day] [month] [year] [list]

Message-ID: <20140715132946.771def89@canb.auug.org.au>
Date:	Tue, 15 Jul 2014 13:29:46 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Mauro Carvalho Chehab <mchehab@...radead.org>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Guenter Roeck <linux@...ck-us.net>
Subject: linux-next: build failure after merge of the v4l-dvb tree

Hi Mauro,

After merging the v4l-dvb tree, today's linux-next build (powerpc ppc64_defconfig)
failed like this:

arch/powerpc/kernel/smp.c:764:2: error: initialization from incompatible pointer type [-Werror]
  { cpu_smt_mask, powerpc_smt_flags, SD_INIT_NAME(SMT) },
  ^
arch/powerpc/kernel/smp.c:764:2: error: (near initialization for 'powerpc_topology[0].sd_flags') [-Werror]

Caused by commit 6a0b50087a89 ("Merge branch 'patchwork' into
to_next").  The change to include/linux/sched.h in this merge commit
does not seem to appear in either of the parents of the merge.

Its also a change that (when suggested) was shown to cause more
problems than it was worth and dropped.  I can't imagine how it ended
up in the merge commit.

I have used the v4l-dvb tree from next-20140714 for today.  Please fix
this up.
-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)