Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751988AbeAIJXn (ORCPT + 1 other); Tue, 9 Jan 2018 04:23:43 -0500 Received: from mail.linuxfoundation.org ([140.211.169.12]:52174 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751071AbeAIJXk (ORCPT ); Tue, 9 Jan 2018 04:23:40 -0500 Date: Tue, 9 Jan 2018 10:23:39 +0100 From: Greg Kroah-Hartman To: Guenter Roeck Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org, akpm@linux-foundation.org, shuahkh@osg.samsung.com, patches@kernelci.org, ben.hutchings@codethink.co.uk, lkft-triage@lists.linaro.org, stable@vger.kernel.org Subject: Re: [PATCH 4.4 00/22] 4.4.111-stable review Message-ID: <20180109092339.GA30075@kroah.com> References: <20180108125925.601688333@linuxfoundation.org> <20180108232907.GA22001@roeck-us.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20180108232907.GA22001@roeck-us.net> User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Mon, Jan 08, 2018 at 03:29:07PM -0800, Guenter Roeck wrote: > On Mon, Jan 08, 2018 at 01:59:27PM +0100, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.4.111 release. > > There are 22 patches in this series, all will be posted as a response > > to this one. If anyone has any issues with these being applied, please > > let me know. > > > > Responses should be made by Wed Jan 10 12:59:14 UTC 2018. > > Anything received after that time might be too late. > > > > x86:64:allnoconfig still fails to build. > > To reproduce: > make ARCH=x86_64 allnoconfig > make ARCH=x86_64 arch/x86/entry/vdso/vma.o > > arch/x86/entry/vdso/vma.c: In function ‘map_vdso’: > arch/x86/entry/vdso/vma.c:175:9: error: > implicit declaration of function ‘pvclock_pvti_cpu0_va’ Ok, forcing ARCH=x86_64 shows this now for me, strange it did not without it, which worries me... Anyway, a simple line seems to have solved this, let me push that out now, I couldn't take the full patch you referenced as that causes build errors. thanks, greg k-h