Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp8623407ybl; Thu, 16 Jan 2020 21:10:25 -0800 (PST) X-Google-Smtp-Source: APXvYqw30Zh2i4tTleZtgyiRYwQ47alLVAcOuL3f2J+SzYTN/E+OdJCRAihfD87h49OPEj8TndMG X-Received: by 2002:a9d:3ea:: with SMTP id f97mr4718991otf.42.1579237825618; Thu, 16 Jan 2020 21:10:25 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1579237825; cv=none; d=google.com; s=arc-20160816; b=HjI37AMMX71hP+8+3EzlPXhRkYtLVIxLhFGC6T+rzg8eFBduBTFKk4s1Gczb0bvH79 1aTqTlGDCc1MgjpyPj+sAFj/qQ6KrJaB1FsF+J2Lo5eaCIK9rumoXZWMGRkdgg5wBn2m ld8ANFpJRcEg6vKUw5gkGe9O9gUoSy2V8pgNSSnzlLK7ZHwPpv8knyBz3hvw51lglHxk MuqaKW5M+rzBz8MNyoMDmoCNh/wIYZRdlo3ImELnaWlWycgiqgunSQS49norc2BbFb8T 7k7Fkrz23R2ye6CoOeJxJkwz923XGGGNIIrUlW3h1N4agta+XvRt9T3KXYe6tNZyajau qpEQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=0ZAA6ArE7EFahhPfS+QoCnTMWT223RRIn6fSE0cQ5M4=; b=edWF3Vo0yxYu/OoBu2ViCgt8bXWYP9VbZjMVNt3C4vSdGrdzn4WnEPptwvml3IURkO HpOCTfz5pnJ3JCPMDol3VMBkmvC5C0hn4NKNO92Y0rIKqOqAx5cHzpKt9+3axmFz9B8D HQFJUG9nEhgZ1+8HI2FCl/2c0WhfDUq8YrxszoG1e9s+C+QZbK4yIQDbVthCI8MZnUxv qBd0l3pLW4NzqQVH+ShPtV5/ViVhFWb5d0ZRn5u4jOGpfMu2OIvfU3Cijmes20lblxwC FJYrMPEYDS/5C0AAY656ElqR0vZ7WnI3NwOsRKDDh+TuiL7d+uBlHIpD1T24c15uOyv6 /jqw== 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 l21si12802474oic.126.2020.01.16.21.10.14; Thu, 16 Jan 2020 21:10:25 -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 S1733283AbgAQBcE (ORCPT + 99 others); Thu, 16 Jan 2020 20:32:04 -0500 Received: from ZXSHCAS2.zhaoxin.com ([203.148.12.82]:22532 "EHLO ZXSHCAS2.zhaoxin.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1730070AbgAQBcD (ORCPT ); Thu, 16 Jan 2020 20:32:03 -0500 Received: from zxbjmbx1.zhaoxin.com (10.29.252.163) by ZXSHCAS2.zhaoxin.com (10.28.252.162) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1261.35; Fri, 17 Jan 2020 09:32:01 +0800 Received: from [10.32.64.11] (10.32.64.11) by zxbjmbx1.zhaoxin.com (10.29.252.163) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1261.35; Fri, 17 Jan 2020 09:31:44 +0800 Subject: Re: [PATCH] x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2 To: Borislav Petkov CC: Thomas Gleixner , , , , , , , , , , , , , References: <1579146434-2668-1-git-send-email-TonyWWang-oc@zhaoxin.com> <87r1zzuy48.fsf@nanos.tec.linutronix.de> <20200116180748.GG27148@zn.tnic> From: Tony W Wang-oc Message-ID: Date: Fri, 17 Jan 2020 09:32:10 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <20200116180748.GG27148@zn.tnic> Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.32.64.11] X-ClientProxiedBy: zxbjmbx1.zhaoxin.com (10.29.252.163) To zxbjmbx1.zhaoxin.com (10.29.252.163) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 17/01/2020 02:07, Borislav Petkov wrote: > On Thu, Jan 16, 2020 at 06:09:27PM +0100, Thomas Gleixner wrote: >> So the right thing here is to resend both patches as a patch series >> with the conflict properly resolved. > > And it is about time you started using --thread and --no-chain-reply-to > with git send-email so that your patchsets are properly threaded. See > the git-send-email(1) if something's still unclear. > Ok, will do like this. Sincerely TonyWWang-oc