From: "Naik, Avadhut" <avadnaik@amd.com>
To: Sohil Mehta <sohil.mehta@intel.com>,
Avadhut Naik <avadhut.naik@amd.com>,
linux-trace-kernel@vger.kernel.org, linux-edac@vger.kernel.org
Cc: rostedt@goodmis.org, tony.luck@intel.com, bp@alien8.de,
x86@kernel.org, yazen.ghannam@amd.com
Subject: Re: [PATCH v5 0/2] Update mce_record tracepoint
Date: Thu, 28 Mar 2024 19:13:30 -0500 [thread overview]
Message-ID: <a7246356-98bd-4f8e-9a39-3a2e65b2eded@amd.com> (raw)
In-Reply-To: <9640d452-c591-495b-8284-92f7f986c97d@intel.com>
On 3/28/2024 13:14, Sohil Mehta wrote:
> On 3/28/2024 11:04 AM, Avadhut Naik wrote:
>
>> - Since only caps of words which are not acronyms have been changed in
>> this version and the word "REVISION" has been removed i.e. changes are
>> very minor, have retained the the below tags received for previous
>> versions:
>> Reviewed-by: Sohil Mehta <sohil.mehta@intel.com>
>
>> Avadhut Naik (2):
>> tracing: Include PPIN in mce_record tracepoint
>> tracing: Include Microcode Revision in mce_record tracepoint
>
>
> The patches look good to me.
Kindly ignore this set.
As pointed out by Sohit, have missed adding linux-kernel@vger.kernel.org
Will resend the set.
--
Thanks,
Avadhut Naik
prev parent reply other threads:[~2024-03-29 0:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 18:04 [PATCH v5 0/2] Update mce_record tracepoint Avadhut Naik
2024-03-28 18:04 ` [PATCH v5 1/2] tracing: Include PPIN in " Avadhut Naik
2024-03-29 7:11 ` [PATCH] x86/mce: Clean up TP_printk() output line of the " Ingo Molnar
2024-03-29 16:22 ` Naik, Avadhut
2024-03-29 16:50 ` Luck, Tony
2024-03-29 18:23 ` Naik, Avadhut
2024-03-30 10:38 ` Ingo Molnar
2024-03-28 18:04 ` [PATCH v5 2/2] tracing: Include Microcode Revision in " Avadhut Naik
2024-03-28 18:14 ` [PATCH v5 0/2] Update " Sohil Mehta
2024-03-29 0:13 ` Naik, Avadhut [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=a7246356-98bd-4f8e-9a39-3a2e65b2eded@amd.com \
--to=avadnaik@amd.com \
--cc=avadhut.naik@amd.com \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sohil.mehta@intel.com \
--cc=tony.luck@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).