public inbox for linux-kernel@vger.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: Thu, 19 Jan 2023 17:12:59 +0100	[thread overview]
Message-ID: <Y8lsCzWJv73sBeyj@kroah.com> (raw)
In-Reply-To: <Y8eCA7hdde07a4gz@ziqianlu-desk2>

On Wed, Jan 18, 2023 at 01:22:11PM +0800, Aaron Lu wrote:
> Hi Greg,
> 
> On Mon, Jan 09, 2023 at 03:38:43PM +0800, Aaron Lu wrote:
> > On Sat, Jan 07, 2023 at 09:18:15AM +0100, Greg KH wrote:
> > > 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?
> > 
> > It appears Pavel Boldin's last reply didn't make it to lore for some
> > reason but I saw him kindly replying again and I suppose you should
> > have received it.
> > 
> > But just in case, the link for Pavel's new reply is here:
> > https://lore.kernel.org/lkml/CABohvEPWBHmrRpZcQejTkZ+CYtYCyu6rFMd4doNn_CMk35um+g@mail.gmail.com/
> 
> Now with the original author Pavel Boldin's "LGTM", do you think this
> patch is OK to you or you still insist something else? Please kindly
> let me know, thanks.

I do not see any sort of tag sent by Pavel (hint, you can NOT make one
up yourself) to indicate that they agree with this.

Also, the amount of gyrations you all went through just to keep an
Intel lawyer's name out of the changelog is insane and means that I was
right to push for this.  I still want it now, just because :)

thanks,

greg k-h

  reply	other threads:[~2023-01-20  4:44 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
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 [this message]
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=Y8lsCzWJv73sBeyj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox