All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: David Wang <DavidWang@zhaoxin.com>
Cc: "tony.luck@intel.com" <tony.luck@intel.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Bruce Chang (VAS)" <BruceChang@via-alliance.com>,
	"Cooper Yan(BJ-RD)" <CooperYan@zhaoxin.com>,
	"Qiyuan Wang(BJ-RD)" <QiyuanWang@zhaoxin.com>,
	Benjamin Pan <BenjaminPan@viatech.com>,
	Luke Lin <LukeLin@viacpu.com>,
	"Tim Guo(BJ-RD)" <TimGuo@zhaoxin.com>
Subject: Re: 答复: [PATCH 1/2] x86/mce: new centaur CPUs support MCE broadcasting
Date: Wed, 4 Apr 2018 13:18:22 +0200	[thread overview]
Message-ID: <20180404111822.GA16437@pd.tnic> (raw)
In-Reply-To: <0e48bb8d5dda4c8fbff849a052714524@zhaoxin.com>

On Wed, Apr 04, 2018 at 02:34:52AM +0000, David Wang wrote:
> Those are new processors and main usage of CentaurHauls CPUs in recent
> years is for limited and/or embedded instead of distribution markets.
> So there is no plan or resource to create such document for public
> access. Is public spec mandatory for code check-in? We can provide
> platforms for verification instead.

Nah, not needed. As long as the code paths don't break anything else and
as long as we can CC you to fix bugs people report, we're good. :-)

Btw, please do not top-post on a public ML.

Thx.

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.

WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.de>
To: David Wang <DavidWang@zhaoxin.com>
Cc: "tony.luck@intel.com" <tony.luck@intel.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Bruce Chang (VAS)" <BruceChang@via-alliance.com>,
	"Cooper Yan(BJ-RD)" <CooperYan@zhaoxin.com>,
	"Qiyuan Wang(BJ-RD)" <QiyuanWang@zhaoxin.com>,
	Benjamin Pan <BenjaminPan@viatech.com>,
	Luke Lin <LukeLin@viacpu.com>,
	"Tim Guo(BJ-RD)" <TimGuo@zhaoxin.com>
Subject: [1/2] x86/mce: new centaur CPUs support MCE broadcasting
Date: Wed, 4 Apr 2018 13:18:22 +0200	[thread overview]
Message-ID: <20180404111822.GA16437@pd.tnic> (raw)

On Wed, Apr 04, 2018 at 02:34:52AM +0000, David Wang wrote:
> Those are new processors and main usage of CentaurHauls CPUs in recent
> years is for limited and/or embedded instead of distribution markets.
> So there is no plan or resource to create such document for public
> access. Is public spec mandatory for code check-in? We can provide
> platforms for verification instead.

Nah, not needed. As long as the code paths don't break anything else and
as long as we can CC you to fix bugs people report, we're good. :-)

Btw, please do not top-post on a public ML.

Thx.

  parent reply	other threads:[~2018-04-04 11:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-30  9:53 [PATCH 0/2] MCA support on Centaur CPU David Wang
2018-03-30  9:53 ` [PATCH 1/2] x86/mce: new centaur CPUs support MCE broadcasting David Wang
2018-03-30  9:53   ` [1/2] " davidwang
2018-03-30 10:26   ` [PATCH 1/2] " Borislav Petkov
2018-03-30 10:26     ` [1/2] " Borislav Petkov
     [not found]     ` <0e48bb8d5dda4c8fbff849a052714524@zhaoxin.com>
2018-04-04 11:18       ` Borislav Petkov [this message]
2018-04-04 11:18         ` Borislav Petkov
2018-04-08  2:18         ` 答复: 答复: [PATCH 1/2] " David Wang
2018-04-08  2:18           ` [1/2] " davidwang
2018-03-30  9:53 ` [PATCH 2/2] x86/mce: add CMCI support for centaur CPUs David Wang
2018-03-30  9:53   ` [2/2] " davidwang
2018-03-30 10:41 ` [PATCH 0/2] MCA support on Centaur CPU Ingo Molnar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180404111822.GA16437@pd.tnic \
    --to=bp@alien8.de \
    --cc=BenjaminPan@viatech.com \
    --cc=BruceChang@via-alliance.com \
    --cc=CooperYan@zhaoxin.com \
    --cc=DavidWang@zhaoxin.com \
    --cc=LukeLin@viacpu.com \
    --cc=QiyuanWang@zhaoxin.com \
    --cc=TimGuo@zhaoxin.com \
    --cc=hpa@zytor.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.