You may need to create a patch to workaround the issue first since our PRC team 
is on the national holiday for the week.


Isaku Yamahata wrote:
> Sorry for that.
> This should be fixed by Yu's patches.
> I've been waiting for Yu to respin the patches. Yu?
> If it would take a while, I could create a band aid patch to
> define those symbols.
> thanks,
> On Tue, Sep 30, 2008 at 12:08:04PM +0100, Ian Jackson wrote:
>> Currently the automatic patch forwarding machinery which sits between
>> commits to xen-unstable mainline and the public non-staging tree
>> isn't
>> feeding anything through because the ia64 build is broken:
>> .../xen/drivers/built_in.o: In function `set_px_pminfo':
>> .../xen/drivers/cpufreq/cpufreq.c:226: undefined reference to
>> `get_cpu_id' .../xen/drivers/cpufreq/cpufreq.c:268: undefined
>> reference to `xenpf_copy_px_states'
>> .../xen/drivers/cpufreq/cpufreq.c:303: undefined reference to
>> `cpufreq_cpu_init' This looks like it was introduce in one of these
>> changes:
>> changeset:   18552:19b0a4f91712
>> summary:     x86 and ia64: move cpufreq notify code to commone place
>> changeset:   18551:d1d9915041de
>> summary:     X86 and IA64: Update cpufreq statistic logic for
>> supporting both x86
>> changeset:   18550:08374be21318
>> summary:     X86 and IA64: Rebase cpufreq logic for supporting both
>> x86 and ia64 Perhaps an ia64 part is missing ?
>> It would be nice to get this fixed ...
>> Thanks,
>> Ian.
>> _______________________________________________
>> Xen-ia64-devel mailing list

Xen-ia64-devel mailing list

Reply via email to