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>,
"Lendacky, Thomas" <Thomas.Lendacky@amd.com>,
"Singh, Brijesh" <brijesh.singh@amd.com>
Subject: Re: [PATCH 2/2] x86/mce/amd: Ensure quirks are applied in resume path as well
Date: Wed, 16 Jan 2019 16:26:43 +0100 [thread overview]
Message-ID: <20190116152643.GH15409@zn.tnic> (raw)
In-Reply-To: <8bed39c8-df48-dbb9-3674-dfbc4aea2967@amd.com>
On Wed, Jan 16, 2019 at 03:14:29PM +0000, S wrote:
> Done. Hope the mailer is fine now, i have added --from while sending the
> new patchset and also got it reviewed from folks here.
No, it isn't. And the problem is not git. The problem is your normal emails
you're sending. Look at what you just sent:
https://lore.kernel.org/lkml/8bed39c8-df48-dbb9-3674-dfbc4aea2967@amd.com/raw
and especially your From: field:
From: S@vger.kernel.org
Is that your email address?
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2019-01-16 15:26 UTC|newest]
Thread overview: 20+ 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 [this message]
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
[not found] <1546594609-22403-1-git-send-email-shirish.s@amd.com>
2019-01-04 9:37 ` [PATCH 2/2] x86/mce/amd: Ensure quirks are applied in resume path as well S, Shirish
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=20190116152643.GH15409@zn.tnic \
--to=bp@alien8.de \
--cc=Shirish.S@amd.com \
--cc=Thomas.Lendacky@amd.com \
--cc=brijesh.singh@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
all inboxes | Powered by JetHome®