Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp4985307imm; Tue, 21 Aug 2018 04:31:20 -0700 (PDT) X-Google-Smtp-Source: AA+uWPzOYIdFnNI8r4TPcsTCrH0xksye5KYn9w33HDdNYb4qRoX2CqoExB4AVJSfFwFYXrp4Oe8U X-Received: by 2002:a62:d113:: with SMTP id z19-v6mr52040481pfg.98.1534851080070; Tue, 21 Aug 2018 04:31:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1534851080; cv=none; d=google.com; s=arc-20160816; b=j7uEWhFPMdPBBbKJX6J1XJrc2kiFtilAS34e+Dt0KcoatJz7qGC8vnl1TVy7jbqZ9a F50d96QIgHRGyhONKsPTYxRnKDEw4xiaH51ofyk+XNteOuLbq3+fTMCmG4HI1gligTml tlzvPWgDt/zg1wlI1jejkU4LsuEEGgLj4NepBTAcZGNWcr+ZeOOHiFGvANFZIZ7SOdf1 fV5GmLylSJUOunTyG8xkD3JNYl9iyN0tbQNf0sSvDKAq6usbWx+vYjJqeXhhcmMP76Bt IUT1jFLlV6ajj+/VAKC/bm65RWz3Vez4nMrAN8ab5cybVU+qKtO0ntiyORxZameA8So0 ZIwg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=SB4k0LnwAUL9JgBZ7b1viyVuyhAUWziRCKK6MuuH39s=; b=CIs3eRw8KknpDvCs5ND1r45fosIovIxYFmKoHSXmaZleLyqU4smhyhCumxADySzPvM O4RnoMjOdCTptVaXExKlxiA/1eR9IlugLRc/JW/+5GYxqEm5vt4OPB+AANTxdoABzk7C gFlOCfLbQ2ssUf4wvvBjSJU+5AhegWHK/KuEwwDLGfERYNorwdNsmVojfuruL2lC31ql /qLKk/7PSkfX4OGYOyKq0s+hfUlJ+GxYgqGxZM+zFRCTGf8kDj4GmsspE1qNpqpWilSV xTcx3TAoVuH/GQ6pzj3UZL5eKQUmP6F2q4kwpGc197vF9vInDT7gNLLpbGZyODSt6ioS LVLQ== 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 82-v6si12654460pfo.229.2018.08.21.04.31.05; Tue, 21 Aug 2018 04:31:20 -0700 (PDT) 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 S1726952AbeHUOkR (ORCPT + 99 others); Tue, 21 Aug 2018 10:40:17 -0400 Received: from mail.skyhub.de ([5.9.137.197]:44398 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726798AbeHUOkR (ORCPT ); Tue, 21 Aug 2018 10:40:17 -0400 X-Virus-Scanned: Nedap ESD1 at mail.skyhub.de Received: from mail.skyhub.de ([127.0.0.1]) by localhost (blast.alien8.de [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id N5HaFKT2VKKM; Tue, 21 Aug 2018 13:20:13 +0200 (CEST) Received: from nazgul.tnic (77-85-47-250.ip.btc-net.bg [77.85.47.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id E510A1EC044B; Tue, 21 Aug 2018 13:20:12 +0200 (CEST) Date: Tue, 21 Aug 2018 13:20:20 +0200 From: Borislav Petkov To: Pu Wen Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com, x86@kernel.org, thomas.lendacky@amd.com, pbonzini@redhat.com, mchehab@kernel.org, mikhail.jin@gmail.com, linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, linux-edac@vger.kernel.org Subject: Re: [PATCH v4 15/16] driver/edac: enable Hygon support to AMD64 EDAC driver Message-ID: <20180821112020.GB29972@nazgul.tnic> References: <6275a5a0a0cfbd2c1abc09a5bb41caabecd02e27.1534599097.git.puwen@hygon.cn> <20180821081331.GC24940@nazgul.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 21, 2018 at 07:04:23PM +0800, Pu Wen wrote: > Sure, JV will negotiate with AMD and make sure only JV use family 18h and > AMD won't use family 0x18h, which will make the patch tight and clear. > > What's the best way to adapt for EDAC driver? > * To simplify the code based on AMD won't do family 0x18 and remove > vendor checking. That, provided AMD won't use family 0x18. -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. --