linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Tony W Wang-oc <TonyWWang-oc@zhaoxin.com>
Cc: "tony.luck@intel.com" <tony.luck@intel.com>,
	"Borislav Petkov (bp@alien8.de)" <bp@alien8.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>,
	"yazen.ghannam@amd.com" <yazen.ghannam@amd.com>,
	"vishal.l.verma@intel.com" <vishal.l.verma@intel.com>,
	"qiuxu.zhuo@intel.com" <qiuxu.zhuo@intel.com>,
	David Wang <DavidWang@zhaoxin.com>,
	"Cooper Yan(BJ-RD)" <CooperYan@zhaoxin.com>,
	"Qiyuan Wang(BJ-RD)" <QiyuanWang@zhaoxin.com>,
	"Herry Yang(BJ-RD)" <HerryYang@zhaoxin.com>
Subject: Re: [PATCH v3 2/4] x86/mce: Make 3 functions non-static
Date: Mon, 16 Sep 2019 11:50:30 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1909161148220.10731@nanos.tec.linutronix.de> (raw)
In-Reply-To: <966609ae83b947b998a85cd2fcc1f304@zhaoxin.com>

On Mon, 16 Sep 2019, Tony W Wang-oc wrote:

> On Mon, Sep 16, 2019, Thomas Gleixner wrote:
> >On Wed, 11 Sep 2019, Tony W Wang-oc wrote:
> >
> >> These functions are declared static and cannot be used in others
> >> .c source file. this commit removes the static attribute and adds
> >> the declaration to the header for these functions.
> >
> >I'm not Cc'ed on any patches which use those functions. Please Cc the
> >relevant maintainers on all patches of such a patch series so contect can
> >be seen.
> >
> 
> Patches 3/4, 4/4 in this patchsets are using these functions. Specifically, 
> "[PATCH v3 3/4] x86/mce: Add Zhaoxin CMCI support " in this patchsets is
> using intel_init_cmci(), "[PATCH v3 4/4] x86/mce: Add Zhaoxin LMCE support"
> is using intel_init_lmce() and intel_clear_lmce().
> 
> I had sent all patches in this patchsets to your mailbox. Could you help to
> check again? Thank you.

Found them by now, but please make sure that you provide cover letter
[PATCH vX 0/N ] and thread the patches proper so they reference the cover
letter. git send-email does that for you.

Thanks,

	tglx

  reply	other threads:[~2019-09-16  9:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-16  9:44 [PATCH v3 2/4] x86/mce: Make 3 functions non-static Tony W Wang-oc
2019-09-16  9:50 ` Thomas Gleixner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-09-16 11:36 Tony W Wang-oc
2019-09-16  9:56 Tony W Wang-oc
2019-09-11 12:01 Tony W Wang-oc
2019-09-16  8:13 ` Thomas Gleixner

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=alpine.DEB.2.21.1909161148220.10731@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=CooperYan@zhaoxin.com \
    --cc=DavidWang@zhaoxin.com \
    --cc=HerryYang@zhaoxin.com \
    --cc=QiyuanWang@zhaoxin.com \
    --cc=TonyWWang-oc@zhaoxin.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=qiuxu.zhuo@intel.com \
    --cc=tony.luck@intel.com \
    --cc=vishal.l.verma@intel.com \
    --cc=x86@kernel.org \
    --cc=yazen.ghannam@amd.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).