From: S@vger.kernel.org
To: Borislav Petkov <bp@alien8.de>, "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 0/2] x86/mce/amd: apply missing quirks for family 15 models
Date: Mon, 7 Jan 2019 15:13:49 +0000 [thread overview]
Message-ID: <7d6aa3af-092a-db11-0985-13c2d729340d@amd.com> (raw)
In-Reply-To: <20190107112430.GA28223@nazgul.tnic>
On 1/7/2019 4:54 PM, Borislav Petkov wrote:
> On Mon, Jan 07, 2019 at 10:37:07AM +0000, S, Shirish wrote:
>> This patch series applies to family 15 CPU's of AMD platforms,
>> so as to address a consistent warning of
>> "[Firmware Bug]: cpu 0, invalid threshold interrupt offset"
>> at every boot and upon completiong of successful S3 cycle,
>> due to a missing quirk, which was not extended to newer models
>> and also not applied in resume path.
>>
>> Shirish S (2):
>> x86/mce/amd: Extend "Disable error thresholding bank 4" to more models
>> x86/mce/amd: Ensure quirks are applied in resume path as well
>>
>> arch/x86/kernel/cpu/mce/amd.c | 34 ++++++++++++++++++++++++++++++++++
>> arch/x86/kernel/cpu/mce/core.c | 2 +-
>> 2 files changed, 35 insertions(+), 1 deletion(-)
>>
>> --
> You sent those once three days ago. Why are you sending them again?
> There's no changelog to explain what the difference is from the last
> submission so what's up?
I found that the get_maintainers.pl did not add anyone but me for the
cover letter.
Hence i have re-sent the entire series along with cover letter so that the
reviewers would get context.
> Also, I'd suggest you have more patience.
Sure, I will wait, no worries.
Regards,
Shirish S
> And while you wait, you can
> take a look at
>
> https://www.kernel.org/doc/html/latest/process/submitting-patches.html
>
> to read up on all the modalities when sending patches.
>
> Thx.
>
--
Regards,
Shirish S
prev parent reply other threads:[~2019-01-07 15:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 10:37 [PATCH 0/2] x86/mce/amd: apply missing quirks for family 15 models S, Shirish
2019-01-07 10:37 ` [PATCH 1/2] x86/mce/amd: Extend "Disable error thresholding bank 4" to more models S, Shirish
2019-01-09 21:54 ` Borislav Petkov
2019-01-10 8:02 ` S
2019-01-14 10:26 ` Borislav Petkov
2019-01-07 10:37 ` [PATCH 2/2] x86/mce/amd: Ensure quirks are applied in resume path as well S, Shirish
2019-01-09 22:08 ` Borislav Petkov
2019-01-10 8:04 ` S
2019-01-14 10:33 ` Borislav Petkov
2019-01-14 15:26 ` S
2019-01-14 15:32 ` Borislav Petkov
[not found] ` <4f8b532b-8613-feb5-7474-4bb0462cf1c7@amd.com>
2019-01-15 17:26 ` Borislav Petkov
2019-01-16 15:14 ` S
2019-01-16 15:26 ` Borislav Petkov
2019-01-16 15:31 ` S, Shirish
2019-01-16 15:36 ` S, Shirish
2019-01-16 15:38 ` Borislav Petkov
2019-01-07 11:24 ` [PATCH 0/2] x86/mce/amd: apply missing quirks for family 15 models Borislav Petkov
2019-01-07 15:13 ` S [this message]
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=7d6aa3af-092a-db11-0985-13c2d729340d@amd.com \
--to=s@vger.kernel.org \
--cc=Shirish.S@amd.com \
--cc=bp@alien8.de \
--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