From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754089AbcLAJpw (ORCPT ); Thu, 1 Dec 2016 04:45:52 -0500 Received: from mail-io0-f170.google.com ([209.85.223.170]:33418 "EHLO mail-io0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752437AbcLAJpN (ORCPT ); Thu, 1 Dec 2016 04:45:13 -0500 MIME-Version: 1.0 In-Reply-To: <874m2ooumq.fsf@concordia.ellerman.id.au> References: <1477585631-18574-1-git-send-email-ard.biesheuvel@linaro.org> <1477585631-18574-3-git-send-email-ard.biesheuvel@linaro.org> <87oa13ssqq.fsf@concordia.ellerman.id.au> <874m2ooumq.fsf@concordia.ellerman.id.au> From: Ard Biesheuvel Date: Thu, 1 Dec 2016 09:45:11 +0000 Message-ID: Subject: Re: [PATCH v3 2/3] powerpc/reloc64: add support for 32-bit CRC pseudo-symbols To: Michael Ellerman Cc: "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , jeyu@redhat.com, Will Deacon , Rusty Russell , Andrew Morton , Benjamin Herrenschmidt , "paulus@samba.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 1 December 2016 at 09:39, Michael Ellerman wrote: > Ard Biesheuvel writes: >> On 25 November 2016 at 11:29, Michael Ellerman wrote: >>> Ard Biesheuvel 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 -- Ard.