On Wed, 30 Nov 2011 15:42:31 +1100 Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote:
> Hi Andrew,
>
> After merging the final tree, today's linux-next build (i386 defconfig)
> failed like this:
>
> kernel/cpuset.c: In function 'cpuset_change_task_nodemask':
> kernel/cpuset.c:971:17: error: 'struct task_struct' has no member named 'mempolicy'
>
> Caused by commit abf5d6d23d83 ("cpusets: stall when updating mems_allowed
> for mempolicy or disjoint nodemask") from the akpm tree. The mempolicy
> member is only available when CONFIG_NUMA is set.
>
This obviously can be hacked around, but one wonders whether we really
need to include things like cpuset_change_task_nodemask() in a
CONFIG_NUMA=n vmlinux?
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
