From: tip-bot for Prarit Bhargava <prarit@redhat.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
tglx@linutronix.de, prarit@redhat.com, mingo@elte.hu,
borislav.petkov@amd.com
Subject: [tip:x86/urgent] x86/microcode: Remove noisy AMD microcode warning
Date: Tue, 7 Feb 2012 11:40:56 -0800 [thread overview]
Message-ID: <tip-c1d2f1bccf4259384e581b937e694ee8a350fe55@git.kernel.org> (raw)
In-Reply-To: <1328552935-965-1-git-send-email-prarit@redhat.com>
Commit-ID: c1d2f1bccf4259384e581b937e694ee8a350fe55
Gitweb: http://git.kernel.org/tip/c1d2f1bccf4259384e581b937e694ee8a350fe55
Author: Prarit Bhargava <prarit@redhat.com>
AuthorDate: Mon, 6 Feb 2012 13:28:55 -0500
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Tue, 7 Feb 2012 10:53:42 +0100
x86/microcode: Remove noisy AMD microcode warning
AMD processors will never support /dev/cpu/microcode updating so
just silently fail instead of printing out a warning for every
cpu.
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Cc: Borislav Petkov <borislav.petkov@amd.com>
Link: http://lkml.kernel.org/r/1328552935-965-1-git-send-email-prarit@redhat.com
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
arch/x86/kernel/microcode_amd.c | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/arch/x86/kernel/microcode_amd.c b/arch/x86/kernel/microcode_amd.c
index ac0417b..73465aa 100644
--- a/arch/x86/kernel/microcode_amd.c
+++ b/arch/x86/kernel/microcode_amd.c
@@ -360,7 +360,6 @@ out:
static enum ucode_state
request_microcode_user(int cpu, const void __user *buf, size_t size)
{
- pr_info("AMD microcode update via /dev/cpu/microcode not supported\n");
return UCODE_ERROR;
}
prev parent reply other threads:[~2012-02-07 19:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 18:28 [PATCH] x86, Remove " Prarit Bhargava
2012-02-07 19:40 ` tip-bot for Prarit Bhargava [this message]
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=tip-c1d2f1bccf4259384e581b937e694ee8a350fe55@git.kernel.org \
--to=prarit@redhat.com \
--cc=borislav.petkov@amd.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--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