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]

Message-ID: <53C4BF8E.4010509@roeck-us.net>
Date:	Mon, 14 Jul 2014 22:43:42 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Mauro Carvalho Chehab <mchehab@...radead.org>
CC:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: build failure after merge of the v4l-dvb tree

On 07/14/2014 08:29 PM, Stephen Rothwell wrote:
> 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.
>

Do you mean b6220ad66 (sched: Fix compiler warnings) ? I thought that was accepted
a week or so ago.

Guenter

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