All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	Randy Dunlap <rdunlap@infradead.org>, X86 ML <x86@kernel.org>,
	Arjan van de Ven <arjan@infradead.org>,
	Tigran Aivazian <tigran@aivazian.fsnet.co.uk>
Subject: Re: kernel bugzilla #64531: intel microcode information
Date: Thu, 7 Nov 2013 10:03:25 +0100	[thread overview]
Message-ID: <20131107090325.GB403@gmail.com> (raw)
In-Reply-To: <201311070943.40134.a.miskiewicz@gmail.com>


* Arkadiusz Miskiewicz <a.miskiewicz@gmail.com> wrote:

> On Thursday 07 of November 2013, Randy Dunlap wrote:
> > Re: https://bugzilla.kernel.org/show_bug.cgi?id=64531
> > 
> > 
> > arch/x86/Kconfig line 1053 (+/-), help section in CONFIG_MICROCODE_INTEL,
> > says:
> > 
> > For latest news and information on obtaining all the required
> > Intel ingredients for this driver, check:
> > <http://www.urbanmyth.org/microcode/>
> > 
> > ==> 404  Page not found
> > 
> > 
> > Is there a good replacement for this information or should we just
> > delete that help text?
> 
> For downloading
>  http://downloadcenter.intel.com/ -> search for "processor microcode data 
> file"

How about:

  http://www.intel.com/content/www/us/en/search.html?keyword=linux+microcode+data+file

? That, by the looks of it, appears to be a reasonably stable URL.

Thanks,

	Ingo

  reply	other threads:[~2013-11-07  9:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-07  5:44 kernel bugzilla #64531: intel microcode information Randy Dunlap
2013-11-07  7:34 ` Ingo Molnar
2013-11-07  8:46   ` Arjan van de Ven
2013-11-07 12:10     ` Borislav Petkov
2013-11-07  8:43 ` Arkadiusz Miskiewicz
2013-11-07  9:03   ` Ingo Molnar [this message]
2013-11-07 13:42     ` Henrique de Moraes Holschuh

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=20131107090325.GB403@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.miskiewicz@gmail.com \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=tigran@aivazian.fsnet.co.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.