Received: by 10.223.185.116 with SMTP id b49csp1928554wrg; Thu, 22 Feb 2018 05:34:28 -0800 (PST) X-Google-Smtp-Source: AH8x225GdewHKT5kI8C446X1xmJvYVqZIrv3sFhzpDpPlHAAIYFbfAInQqDJYUA2Y9UwKS9Hi0GR X-Received: by 10.98.133.140 with SMTP id m12mr6948615pfk.226.1519306468328; Thu, 22 Feb 2018 05:34:28 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519306468; cv=none; d=google.com; s=arc-20160816; b=bKL5GiLWmPUfgqQOggR/rG+oYoaLkhmy/XSkD+TvvBw7MCJGYbqxtwMnmB0tN/oYl4 TymXvyd0rFkqNqRuAqWBtD3bwU9hW6xpO1uL/85XyKil/cbb1c495QoRFYtULOZcgb67 3mNwA73iHJI18NZX+pGz6REkDRjQAqQs1vPfsh6t1mgDAx5zM/a11Kkzf6WhcdUqFsWn 7gbWXCw4nUMhMTC9a9VGR2bBE+SA9IJDcjqPI14NESSjPdSOm7uumGxrvJeTsVzFHGH7 5QZQ4CQJoCcy9r9FY55I/FIpNOJYPIUzGDcjb69AkLOc1Xl3/7nUFsmDkB4S1W1PLM6l g5Dw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:references:in-reply-to:date :cc:to:from:subject:message-id:arc-authentication-results; bh=KH1+MED5LBKpK+MVxGXx7cgLCgGePkcQswHdoU8ndeo=; b=pREk9A6Yd4osOt+QDtaS70kWmEaHFeWhwO+6B9+tR6opyU1kQ5mysqbQKaN59aXrFh gMqo8MkU8s6wqVGTFxipInlZIVpY4v7H2e1No3ygGJ0hPlP0HQaJVt3J5H2bxlcxB2Tm 7l0o7BbPVzv6YcB3nFm6ga1UMVux9pXZh9eAMHjMlEHMTJEchDYOW3t6B0ojrmrMdqtr FBgjROOpuughf65Vpnb4lDlswtjLsW8MSwF+hnelRg/ravBtbEXZiuwtSOTB8K7mWGZS 3tgKVyuQJyIgxu/owg/RQxtRT8qF+fQAkh9ZUa5MESlTcJ5izk+Q/dOwbhAA/iFafU15 QeYQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s2si44510pgo.23.2018.02.22.05.34.13; Thu, 22 Feb 2018 05:34:28 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932624AbeBVNcY (ORCPT + 99 others); Thu, 22 Feb 2018 08:32:24 -0500 Received: from pic75-3-78-194-244-226.fbxo.proxad.net ([78.194.244.226]:37798 "EHLO mail.corsac.net" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S932464AbeBVNcW (ORCPT ); Thu, 22 Feb 2018 08:32:22 -0500 Received: from scapa.corsac.net (unknown [IPv6:2a01:e34:ec2f:4e21::1]) by mail.corsac.net (Postfix) with ESMTPS id ABD3898 for ; Thu, 22 Feb 2018 14:32:20 +0100 (CET) Received: from corsac (uid 1000) (envelope-from corsac@debian.org) id a016b by scapa.corsac.net (DragonFly Mail Agent v0.11); Thu, 22 Feb 2018 14:32:20 +0100 Message-ID: <1519306335.2388.18.camel@debian.org> Subject: Re: [PATCH 4.9 34/77] powerpc: fix build errors in stable tree From: Yves-Alexis Perez To: Michael Ellerman , Greg Kroah-Hartman , linux-kernel@vger.kernel.org Cc: stable@vger.kernel.org, Guenter Roeck , Nicholas Piggin Date: Thu, 22 Feb 2018 14:32:15 +0100 In-Reply-To: <874lm9qi4t.fsf@concordia.ellerman.id.au> References: <20180221124432.172390020@linuxfoundation.org> <20180221124433.618725458@linuxfoundation.org> <87k1v5rg66.fsf@concordia.ellerman.id.au> <1519292030.2388.14.camel@debian.org> <874lm9qi4t.fsf@concordia.ellerman.id.au> Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-hCeylf1X0b8M/tlX1zNP" X-Mailer: Evolution 3.26.5-1 Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --=-hCeylf1X0b8M/tlX1zNP Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 2018-02-23 at 00:16 +1100, Michael Ellerman wrote: > With the patches I just sent, for pseries and powernv, the mitigation > should be in place. On machines with updated firmware we'll use the > hardware-assisted L1 flush, otherwise we fallback to doing it in > software. So as of 4.9.82 meltdown is *not* addressed on those arches, but it should = be ok in 4.9.83 or 4.9.84 depending on when the patches are merged? Regards, --=20 Yves-Alexis --=-hCeylf1X0b8M/tlX1zNP Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlqOxl8ACgkQ3rYcyPpX RFvslwf/aVnI05Nuqs39CHZJH9buIEFm2KLU2TmrvUGPHEN8yGg4AHlePfQCVuRw jAHRYvIgdW318xR6cuq5qyjwfTivHb8LVKidP338g/7oZ7/y/gJvIjZnEQZoSmnA 0LVuNtjtGvCSvwSoRxBUS70/ScrVddUdgtpz53PZC1JT+ZDHn/41zkMX5ykpYRxz wqDvk3yhV/8fL9KINROMUXyK3rARCxie4D6C0O6K9vYhx4S3KapEx7jG9fvji5ww Dv9aPLBYk6QyzfGwg9JnKA+IBSMId7Sxc2UhxwfNxr+IvrOqcKLgyUC3WUVHMf3a LdElfT1BeQkS5muGvN+jqgehUCvrdA== =SY45 -----END PGP SIGNATURE----- --=-hCeylf1X0b8M/tlX1zNP--