On 1 December 2016 at 09:45, Ard Biesheuvel <ard.biesheu...@linaro.org> wrote:
> On 1 December 2016 at 09:39, Michael Ellerman <m...@ellerman.id.au> wrote:
>> Ard Biesheuvel <ard.biesheu...@linaro.org> writes:
>>> On 25 November 2016 at 11:29, Michael Ellerman <m...@ellerman.id.au> wrote:
>>>> Ard Biesheuvel <ard.biesheu...@linaro.org> writes:
>>>>
>>>> [    7.607687] kvm: disagrees about version of symbol module_layout
>>>> [    7.846799] virtio: disagrees about version of symbol module_layout
>>>> [   22.012615] crc32c_vpmsum: disagrees about version of symbol 
>>>> module_layout
>>>> [   22.012959] libcrc32c: disagrees about version of symbol module_layout
>>>>
>>>
>>> Sigh. I suppose your modversions fixes are queued for v4.10? It's
>>> probably best to revisit this after the v4.10 merge window closes
>>> then, just to make sure I'm not aiming for a moving target.
>>
>> Actually they were merged into 4.9-rc7 ish.
>>
>> But I'm still seeing the same as above with this series rebased on top
>> of that, and I'm a bit short on time to debug it ATM.
>>
>> So during the 4.10 cycle is probably the best we can hope for, sorry.
>>
>
> Not a problem. The only question is whether 1/3 of this series fixes
> an actual bug or not, given that the CONFIG_RELOCATABLE workaround has
> been made ppc64 only.
>
> But for the remaining patches, I'm happy to respin after the v4.10
> merge window closes, and get something queued for v4.11
>

Actually, given the uncertain fate of modversions in general, we may
no longer have to bother by the time the v4.11 merge window opens ...

Reply via email to