From: Aaron Lu <aaron.lu@intel.com>
To: Pavel Boldin <boldin.pavel@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
"Raphael S. Carvalho" <raphaelsc@scylladb.com>,
Dave Hansen <dave.hansen@intel.com>,
Igor Seletskiy <i@cloudlinux.com>, Moritz Lipp <github@mlq.me>,
Daniel Gruss <daniel.gruss@iaik.tugraz.at>,
Michael Schwarz <michael.schwarz91@gmail.com>,
<linux-kselftest@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] selftest/x86/meltdown: Add a selftest for meltdown
Date: Wed, 18 Jan 2023 13:20:05 +0800 [thread overview]
Message-ID: <Y8eBhaHgICkwR03N@ziqianlu-desk2> (raw)
In-Reply-To: <Y7vK4NDlpfvr9zA1@ziqianlu-desk2>
Hi Pavel,
Hope everything is well.
I wonder if you have missed my last email? Is it OK for me to add your
reviewed-by tag to this patch?
Thanks.
On Mon, Jan 09, 2023 at 04:05:52PM +0800, Aaron Lu wrote:
> Hi Pavel,
>
> On Sat, Jan 07, 2023 at 10:50:44AM +0200, Pavel Boldin wrote:
> > On Sat, Jan 07, 2023 at 10:18, Greg KH <gregkh@linuxfoundation.org>:
> > >
> > > On Fri, Jan 06, 2023 at 09:00:21AM +0800, Aaron Lu wrote:
> > > > If you do not trust what I've done is what I've claimed, now the
> > > > original author Pavel Boldin has given the patch a "LGTM" tag, does that
> > > > address your concern?
> > >
> > > I don't see that anywhere on lore.kernel.org, have a link to it?
> >
> > LGTM.
>
> Thanks for the review.
>
> In Linux kernel community, reviewer normally gives a Reviewed-by tag
> when they think the patch "LGTM". And in this case, it would be a tag
> like this:
>
> Reviewed-by: Pavel Boldin <boldin.pavel@gmail.com>
>
> May I translate your "LGTM" tag to the above Reviewed-by tag?
>
> BTW, the kernel community's explanation of Reviewed-by tag is here in
> case you want to take a look:
> https://docs.kernel.org/process/submitting-patches.html#reviewer-s-statement-of-oversight
>
> Thanks,
> Aaron
next prev parent reply other threads:[~2023-01-18 5:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 12:35 Aaron Lu
2023-01-05 13:42 ` Greg KH
2023-01-05 14:11 ` Raphael S. Carvalho
2023-01-05 14:38 ` Greg KH
2023-01-05 15:26 ` Dave Hansen
2023-01-06 1:00 ` Aaron Lu
2023-01-07 8:18 ` Greg KH
2023-01-07 8:50 ` Pavel Boldin
2023-01-09 8:05 ` Aaron Lu
2023-01-18 5:20 ` Aaron Lu [this message]
2023-01-09 7:38 ` Aaron Lu
2023-01-18 5:22 ` Aaron Lu
2023-01-19 16:12 ` Greg KH
2023-01-20 2:14 ` Lu, Aaron
2023-01-19 17:15 ` Pavel Boldin
2023-01-20 2:10 ` Lu, Aaron
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=Y8eBhaHgICkwR03N@ziqianlu-desk2 \
--to=aaron.lu@intel.com \
--cc=boldin.pavel@gmail.com \
--cc=daniel.gruss@iaik.tugraz.at \
--cc=dave.hansen@intel.com \
--cc=github@mlq.me \
--cc=gregkh@linuxfoundation.org \
--cc=i@cloudlinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=michael.schwarz91@gmail.com \
--cc=raphaelsc@scylladb.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
all inboxes | Powered by JetHome®