Re: [PATCH] powerpc/powernv: Select CONFIG_PRINTK to fix build failure
From: Pranith Kumar
Date: Tue Dec 30 2014 - 00:47:27 EST
On Mon, Dec 29, 2014 at 4:01 AM, Michael Ellerman <mpe@xxxxxxxxxxxxxx> wrote:
> On Sat, 2014-12-27 at 12:17 -0500, Pranith Kumar wrote:
>> In an allnoconfig we get the following build failure:
> An allnoconfig doesn't include CONFIG_PPC_POWERNV? But I think I know what you
>> arch/powerpc/platforms/built-in.o: In function `.__machine_initcall_powernv_opal_init':
>> opal.c:(.init.text+0x468): undefined reference to `.log_buf_addr_get'
>> opal.c:(.init.text+0x474): undefined reference to `.log_buf_len_get'
>> make: *** [vmlinux] Error 1
>> This happens because powernv requires printk() support. Enable it in the config
> Sort of. It just requires those two routines. Or is there a stronger
> I think the better fix is for those two routines to be defined for
> CONFIG_PRINTK=n, but return NULL and zero respectively.
> And the opal code could skip registering the region when they return NULL/zero.
> Care to do a couple of patches?
Sure, I will give it a try. Thanks for the review!
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/