From: Borislav Petkov <bp@alien8.de>
To: "S, Shirish" <Shirish.S@amd.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H . Peter Anvin" <hpa@zytor.com>,
"maintainer : X86 ARCHITECTURE" <x86@kernel.org>,
Tony Luck <tony.luck@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
"open list : X86 ARCHITECTURE" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] x86/mce/amd: carve out MC4_MISC thresholding quirk
Date: Thu, 17 Jan 2019 11:09:15 +0100 [thread overview]
Message-ID: <20190117100915.GA5023@zn.tnic> (raw)
In-Reply-To: <e65fd961-529e-d479-a269-10267596ec86@amd.com>
On Thu, Jan 17, 2019 at 06:06:06AM +0000, S wrote:
> Thanks for the support, i shall follow the practice from next patch onwards.
Ok, but this mail is still broken. I see:
From: S
To: Borislav Petkov <bp@alien8.de>, "S, Shirish" <Shirish.S@amd.com>
CC: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@redhat.com>,
So I leave it up to you to pay attention to it and to fix it - I think
I've pointed it to you enough times already.
In case you're wondering why you're not getting replies to your mails,
you'll know why.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2019-01-17 10:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 15:10 [PATCH 0/2] x86/mce/amd: apply missing quirks to family 15 models (v2) S, Shirish
2019-01-16 15:10 ` [PATCH 1/2] x86/mce/amd: apply MC4_MISC thresholding to all models of family 15 S, Shirish
2019-01-16 15:10 ` [PATCH 2/2] x86/mce/amd: carve out MC4_MISC thresholding quirk S, Shirish
2019-01-16 19:25 ` Borislav Petkov
2019-01-17 6:06 ` S
2019-01-17 10:09 ` Borislav Petkov [this message]
2019-01-16 19:31 ` [tip:ras/core] x86/MCE/AMD: Carve out the " tip-bot for Shirish S
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=20190117100915.GA5023@zn.tnic \
--to=bp@alien8.de \
--cc=Shirish.S@amd.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=vishal.l.verma@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome