From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.3 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_PASS,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 279E8C04EB8 for ; Sun, 2 Dec 2018 15:17:50 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id DBBF220851 for ; Sun, 2 Dec 2018 15:17:49 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="ufBDOHwO" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org DBBF220851 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725901AbeLBPRo (ORCPT ); Sun, 2 Dec 2018 10:17:44 -0500 Received: from mail.kernel.org ([198.145.29.99]:51610 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725869AbeLBPRo (ORCPT ); Sun, 2 Dec 2018 10:17:44 -0500 Received: from localhost (unknown [213.57.143.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id B7DA220851; Sun, 2 Dec 2018 15:17:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1543763860; bh=S5xtB4Y6bbu4ZPMtbjg5y5hLua/8P4G8EdXSqv/4TeQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ufBDOHwOax/0N9cubBWZVYUsPfObCdHp+9EJrTtpt0RnveYh1Jp0+vkcmVkTEd058 DBYgQClzatkr2wU3Z7ryaJCE4b07SesRaefmJuqllnUNXz9rNbgbCDYd/KwsGwIxeg DLS1VYt/WPZHxJnCWVrywVRimvB/ig5RhT60nWRQ= Date: Sun, 2 Dec 2018 10:17:32 -0500 From: Sasha Levin To: Greg Kroah-Hartman Cc: Russell King - ARM Linux , linux-kernel@vger.kernel.org, stable@vger.kernel.org, Julien Thierry Subject: Re: [PATCH 3.18 14/83] ARM: make lookup_processor_type() non-__init Message-ID: <20181202151732.GH221015@sasha-vm> References: <20181129140138.002176596@linuxfoundation.org> <20181129140138.869602566@linuxfoundation.org> <20181129142817.GW30658@n2100.armlinux.org.uk> <20181130151554.GA29005@kroah.com> <20181130151843.GB29005@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20181130151843.GB29005@kroah.com> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Nov 30, 2018 at 04:18:43PM +0100, Greg Kroah-Hartman wrote: >On Fri, Nov 30, 2018 at 04:15:54PM +0100, Greg Kroah-Hartman wrote: >> On Thu, Nov 29, 2018 at 02:28:18PM +0000, Russell King - ARM Linux wrote: >> > Hi, >> > >> > As I've already fed back to Sascha about this, this patch on its own >> > does not fix anything, and is not a stable kernel candidate without >> > a patch that makes use of it (iow, the spectre fixes.) It is a >> > preparatory patch for mainline commit 383fb3ee8024. >> > >> > Every commit in: >> > >> > $ git rev-list v4.16..383fb3ee8024 >> > >> > are the ARM spectre fixes, which are being back-ported by David Long. >> > >> > Please do not cherry-pick commits from within this series for _any_ >> > stable kernel, but please wait for David to send you the back-ported >> > patches. >> >> Ugh, ok, that's a bunch here. > >Ok, not that bad, only 4: > 383fb3ee8024 ("ARM: spectre-v2: per-CPU vtables to work around big.Little systems") > e209950fdd06 ("ARM: add PROC_VTABLE and PROC_TABLE macros") > 945aceb1db88 ("ARM: clean up per-processor check_bugs method call") > 899a42f83667 ("ARM: make lookup_processor_type() non-__init") > >I'll go drop them all from the trees now. Turns out for 4.14 one of >these patches broke the build anyway. Sasha, how did that past your >builder tests? Because it builds :) -- Thanks, Sasha