From: Joe Perches <joe@perches.com>
To: Jacob Shin <jacob.shin@amd.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
x86@kernel.org, Fenghua Yu <fenghua.yu@intel.com>,
Andreas Herrmann <herrmann.der.user@googlemail.com>,
Borislav Petkov <bp@alien8.de>,
linux-kernel@vger.kernel.org, Borislav Petkov <bp@suse.de>
Subject: Re: [PATCH V2 2/3] x86, microcode, intel: Correct typo in printk
Date: Thu, 23 May 2013 11:12:49 -0700 [thread overview]
Message-ID: <1369332769.2075.23.camel@joe-AO722> (raw)
In-Reply-To: <1369323618-5820-3-git-send-email-jacob.shin@amd.com>
On Thu, 2013-05-23 at 10:40 -0500, Jacob Shin wrote:
> User-visible so correct it.
[]
> diff --git a/arch/x86/kernel/microcode_intel_early.c b/arch/x86/kernel/microcode_intel_early.c
[]
> @@ -529,7 +529,7 @@ int save_mc_for_early(u8 *mc)
[]
> - pr_err("Can not save microcode patch.\n");
> + pr_err("Cannot save microcode patches from initrd.\n");
It seems you enhanced the message rather than fixed
a typo so I think the subject line isn't correct.
next prev parent reply other threads:[~2013-05-23 18:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 15:40 [PATCH V2 0/3] x86/microcode: early microcode patch loading support on AMD Jacob Shin
2013-05-23 15:40 ` [PATCH V2 1/3] x86/microcode: vendor abstract out save_microcode_in_initrd() Jacob Shin
2013-05-28 14:28 ` Borislav Petkov
2013-05-23 15:40 ` [PATCH V2 2/3] x86, microcode, intel: Correct typo in printk Jacob Shin
2013-05-23 18:12 ` Joe Perches [this message]
2013-05-24 8:43 ` Borislav Petkov
2013-05-24 14:11 ` Jacob Shin
2013-05-23 15:40 ` [PATCH V2 3/3] x86/microcode: early microcode patch loading support on AMD Jacob Shin
2013-05-24 15:33 ` Yu, Fenghua
2013-05-24 19:50 ` Jacob Shin
2013-05-28 8:13 ` Borislav Petkov
2013-05-28 22:45 ` Borislav Petkov
2013-05-28 23:43 ` Jacob Shin
2013-05-29 11:06 ` Borislav Petkov
2013-05-23 21:01 ` [PATCH V2 0/3] " Yu, Fenghua
2013-05-23 21:23 ` Jacob Shin
2013-05-24 8:29 ` Borislav Petkov
2013-05-24 14:12 ` Jacob Shin
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=1369332769.2075.23.camel@joe-AO722 \
--to=joe@perches.com \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=fenghua.yu@intel.com \
--cc=herrmann.der.user@googlemail.com \
--cc=hpa@zytor.com \
--cc=jacob.shin@amd.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