From mboxrd@z Thu Jan 1 00:00:00 1970 From: gregkh@linuxfoundation.org (Greg Kroah-Hartman) Date: Thu, 13 Sep 2018 09:12:16 +0200 Subject: [4.14.y] request commit 94a5d8790e79 ("arm64: cpu_errata: include required headers") In-Reply-To: <20180911170030.650928d8@xhacker.debian> References: <20180911170030.650928d8@xhacker.debian> Message-ID: <20180913071216.GH11496@kroah.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Tue, Sep 11, 2018 at 05:00:30PM +0800, Jisheng Zhang wrote: > Hi Greg, > > I think we missed the commit 94a5d8790e79 ("arm64: cpu_errata: include > required headers"), could you please include it in next stable release? Really, you are seeing build failures on 4.14.y without this patch applied? I haven't gotten any reports of this, what is wrong with our build tests that this isn't being caught? thanks, greg k-h From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linuxfoundation.org ([140.211.169.12]:40990 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726694AbeIMMUa (ORCPT ); Thu, 13 Sep 2018 08:20:30 -0400 Date: Thu, 13 Sep 2018 09:12:16 +0200 From: Greg Kroah-Hartman To: Jisheng Zhang Cc: linux-arm-kernel@lists.infradead.org, stable@vger.kernel.org, Arnd Bergmann Subject: Re: [4.14.y] request commit 94a5d8790e79 ("arm64: cpu_errata: include required headers") Message-ID: <20180913071216.GH11496@kroah.com> References: <20180911170030.650928d8@xhacker.debian> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180911170030.650928d8@xhacker.debian> Sender: stable-owner@vger.kernel.org List-ID: On Tue, Sep 11, 2018 at 05:00:30PM +0800, Jisheng Zhang wrote: > Hi Greg, > > I think we missed the commit 94a5d8790e79 ("arm64: cpu_errata: include > required headers"), could you please include it in next stable release? Really, you are seeing build failures on 4.14.y without this patch applied? I haven't gotten any reports of this, what is wrong with our build tests that this isn't being caught? thanks, greg k-h