public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicolai Stange <nicstange@gmail.com>
To: Nicolai Stange <nicstange@gmail.com>
Cc: Borislav Petkov <bp@alien8.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arch/x86/kernel/cpu/microcode/intel: don't store initrd's start
Date: Mon, 25 Jul 2016 15:06:26 +0200	[thread overview]
Message-ID: <87wpk9j299.fsf@gmail.com> (raw)
In-Reply-To: <871t2hkh4w.fsf@gmail.com> (Nicolai Stange's message of "Mon, 25 Jul 2016 14:59:43 +0200")

Nicolai Stange <nicstange@gmail.com> writes:

> Borislav Petkov <bp@alien8.de> writes:
>
>> ---
>> diff --git a/arch/x86/kernel/cpu/microcode/intel.c b/arch/x86/kernel/cpu/microcode/intel.c
>> index 6515c802346a..b98e016ba5fc 100644
>> --- a/arch/x86/kernel/cpu/microcode/intel.c
>> +++ b/arch/x86/kernel/cpu/microcode/intel.c
>> @@ -793,10 +793,10 @@ void __init load_ucode_intel_bsp(void)
>>  void load_ucode_intel_ap(void)
>>  {
>>  	struct ucode_blobs *blobs_p;
>> +	unsigned long *ptrs, start;
>>  	struct mc_saved_data *mcs;
>>  	struct ucode_cpu_info uci;
>>  	enum ucode_state ret;
>> -	unsigned long *ptrs;
>>  
>>  #ifdef CONFIG_X86_32
>>  	mcs	= (struct mc_saved_data *)__pa_nodebug(&mc_saved_data);
>
> Am I overlooking something or is this an unrelated cleanup?

I did, nvm.

  reply	other threads:[~2016-07-25 13:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-24 15:05 [PATCH] arch/x86/kernel/cpu/microcode/intel: don't store initrd's start Nicolai Stange
2016-07-25  7:06 ` Borislav Petkov
2016-07-25  9:24   ` Nicolai Stange
2016-07-25 12:36     ` Borislav Petkov
2016-07-25 12:59       ` Nicolai Stange
2016-07-25 13:06         ` Nicolai Stange [this message]
2016-07-25 13:44         ` Borislav Petkov
2016-07-25 14:16           ` Nicolai Stange
2016-07-25 14:27             ` Nicolai Stange
2016-07-25 16:40               ` Borislav Petkov
2016-07-25 15:07             ` Borislav Petkov
2016-07-25 16:46             ` Borislav Petkov
2016-07-25 17:44               ` Nicolai Stange
2016-07-25 18:18                 ` 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=87wpk9j299.fsf@gmail.com \
    --to=nicstange@gmail.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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