Re: [PATCH 3.2 000/125] 3.2.61-rc1 review

[Guenter Roeck]

On 07/08/2014 12:01 PM, Ben Hutchings wrote:
> This is the start of the stable review cycle for the 3.2.61 release.
> There are 125 patches in this series, which will be posted as responses
> to this one.  If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Thu Jul 10 19:01:49 UTC 2014.
> Anything received after that time might be too late.

Build results:
	total: 109 pass: 71 fail: 38
Failed builds:
	alpha:allmodconfig
	arm:defconfig
	arm:imx_v4_v5_defconfig
	arm:mxs_defconfig
	arm:dove_defconfig
	arm:kirkwood_defconfig
	arm:omap2plus_defconfig
	arm:tegra_defconfig
	arm:u8500_defconfig
	arm:at91sam9rl_defconfig
	arm:pxa910_defconfig
	arm:mackerel_defconfig
	arm:ixp4xx_defconfig
	arm:vexpress_defconfig
	arm:msm_defconfig
	arm:at91rm9200_defconfig
	arm:at91sam9263_defconfig
	arm:at91sam9g45_defconfig
	arm:assabet_defconfig
	i386:defconfig
	i386:allyesconfig
	i386:allmodconfig
	m32r:defconfig
	microblaze:mmu_defconfig
	microblaze:nommu_defconfig
	mips:defconfig
	mips:allmodconfig
	mips:bcm47xx_defconfig
	mips:bcm63xx_defconfig
	mips:ar7_defconfig
	mips:fuloong2e_defconfig
	mips:malta_defconfig
	score:defconfig
	sparc64:allmodconfig
	um:defconfig
	unicore32:defconfig
	xtensa:defconfig
	xtensa:allmodconfig

Qemu images fail to build for mips, mips64, and x86.

Build error seems to be always the same.

lib/nlattr.c: In function 'nla_parse':
lib/nlattr.c:201:3: error: dereferencing pointer to incomplete type
make[1]: *** [lib/nlattr.o] Error 1

Culprit is bfc5184b69 (netlink: rate-limit leftover bytes warning
and print process name). In 3.2, it is necessary to include <linux/sched.h>
explicitly to get the definition of 'struct task_struct'.

Details are available at http://server.roeck-us.net:8010/builders.

Guenter

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