From: tip-bot for Alan <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, alan@linux.intel.com,
gnomes@lxorguk.ukuu.org.uk, hpa@zytor.com, mingo@kernel.org,
tglx@linutronix.de
Subject: [tip:x86/urgent] x86, doc, kconfig: Fix dud URL for Microcode data
Date: Mon, 20 Jan 2014 10:16:21 -0800 [thread overview]
Message-ID: <tip-b8989db9d82465bf38a48a4d3ef32e7d8afc4d08@git.kernel.org> (raw)
In-Reply-To: <20140120180056.7173.62222.stgit@alan.etchedpixels.co.uk>
Commit-ID: b8989db9d82465bf38a48a4d3ef32e7d8afc4d08
Gitweb: http://git.kernel.org/tip/b8989db9d82465bf38a48a4d3ef32e7d8afc4d08
Author: Alan <gnomes@lxorguk.ukuu.org.uk>
AuthorDate: Mon, 20 Jan 2014 18:01:56 +0000
Committer: H. Peter Anvin <hpa@zytor.com>
CommitDate: Mon, 20 Jan 2014 10:12:29 -0800
x86, doc, kconfig: Fix dud URL for Microcode data
The actual data lives in the Intel download center, and that ought to also
be a reliable way to continue to find it. Unfortunately the actual URL
needed for doing it directly is about a foot long so give instructions.
Signed-off-by: Alan Cox <alan@linux.intel.com>
Link: http://lkml.kernel.org/r/20140120180056.7173.62222.stgit@alan.etchedpixels.co.uk
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
---
arch/x86/Kconfig | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 0952ecd..64199bc 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -1064,9 +1064,9 @@ config MICROCODE_INTEL
This options enables microcode patch loading support for Intel
processors.
- For latest news and information on obtaining all the required
- Intel ingredients for this driver, check:
- <http://www.urbanmyth.org/microcode/>.
+ For the current Intel microcode data package go to
+ <https://downloadcenter.intel.com> and search for
+ 'Linux Processor Microcode Data File'.
config MICROCODE_AMD
bool "AMD microcode loading support"
parent reply other threads:[~2014-01-20 18:16 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20140120180056.7173.62222.stgit@alan.etchedpixels.co.uk>]
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-b8989db9d82465bf38a48a4d3ef32e7d8afc4d08@git.kernel.org \
--to=tipbot@zytor.com \
--cc=alan@linux.intel.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@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