From: Greg KH <gregkh@linuxfoundation.org>
To: Evalds Iodzevics <evalds.iodzevics@gmail.com>
Cc: linux-kernel@vger.kernel.org, Borislav Petkov <bp@suse.de>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 1/2] x86/CPU: Add native CPUID variants returning a single datum
Date: Sun, 19 Apr 2020 18:54:34 +0200 [thread overview]
Message-ID: <20200419165434.GA3697654@kroah.com> (raw)
In-Reply-To: <20200419162943.3704-1-evalds.iodzevics@gmail.com>
On Sun, Apr 19, 2020 at 07:29:42PM +0300, Evalds Iodzevics wrote:
> From: Borislav Petkov <bp@suse.de>
>
> ... similarly to the cpuid_<reg>() variants.
>
> Signed-off-by: Borislav Petkov <bp@suse.de>
> Link: http://lkml.kernel.org/r/20170109114147.5082-2-bp@alien8.de
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> ---
> arch/x86/include/asm/processor.h | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
Why are you resending patches from someone else?
next prev parent reply other threads:[~2020-04-19 16:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 16:29 Evalds Iodzevics
2020-04-19 16:29 ` [PATCH 2/2] Fixed broken microcode early loading on 32 bit platforms because it always jumps past cpuid in sync_core() as data structure boot_cpu_data are not populated so early in boot. This is for 4.4. Should be done for 4.9 too Evalds Iodzevics
2020-04-19 16:54 ` Greg KH
2020-04-20 5:52 ` Evalds Iodzevics
2020-04-20 6:07 ` Greg KH
2020-04-19 16:54 ` Greg KH [this message]
2020-04-20 5:52 ` [PATCH 1/2] x86/CPU: Add native CPUID variants returning a single datum Evalds Iodzevics
2020-04-20 6:07 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2016-12-28 4:39 [PATCH] x86: Fix Intel microcode revision detection Junichi Nomura
2016-12-28 11:18 ` Borislav Petkov
2016-12-28 11:20 ` [PATCH 1/2] x86/CPU: Add native CPUID variants returning a single datum Borislav Petkov
2016-12-28 18:11 ` Andy Lutomirski
2016-12-29 9:30 ` Borislav Petkov
2016-12-31 2:13 ` Andy Lutomirski
2016-12-31 11:09 ` Borislav Petkov
2017-01-03 18:35 ` Andy Lutomirski
2017-01-03 19:48 ` Borislav Petkov
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=20200419165434.GA3697654@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bp@suse.de \
--cc=evalds.iodzevics@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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
Powered by JetHome