All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Aaron Lu <aaron.lu@intel.com>
Cc: "Raphael S. Carvalho" <raphaelsc@scylladb.com>,
	Dave Hansen <dave.hansen@intel.com>,
	Igor Seletskiy <i@cloudlinux.com>,
	Pavel Boldin <boldin.pavel@gmail.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: Sat, 7 Jan 2023 09:18:15 +0100	[thread overview]
Message-ID: <Y7kqx5cBCVojq6QJ@kroah.com> (raw)
In-Reply-To: <Y7dypc4sFcmYlXQQ@ziqianlu-desk2>

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?

thanks,

greg k-h

  reply	other threads:[~2023-01-07  8:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-05 12:35 [PATCH] selftest/x86/meltdown: Add a selftest for meltdown 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 [this message]
2023-01-07  8:50           ` Pavel Boldin
2023-01-09  8:05             ` Aaron Lu
2023-01-18  5:20               ` Aaron Lu
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=Y7kqx5cBCVojq6QJ@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.