From: Borislav Petkov <bp@alien8.de>
To: Arjan van de Ven <arjanvandeven@gmail.com>
Cc: Ingo Molnar <mingo@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
LKML <linux-kernel@vger.kernel.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 13:10:14 +0100 [thread overview]
Message-ID: <20131107121014.GB27116@x1.alien8.de> (raw)
In-Reply-To: <CADyApD25k63K1t9SXv7EERopk3sCE9Wq65fiGiFAn_zuPHsd5Q@mail.gmail.com>
On Thu, Nov 07, 2013 at 09:46:40AM +0100, Arjan van de Ven wrote:
> fwiw this file lives on intel.com for a while now.. unfortunately it's
> one of these websites with fancy downloading stuff for which I suspect
> the URLs are not long term stable ;-(
> but if you type "microcode" into the search box its the first entry...
>
> On Thu, Nov 7, 2013 at 8:34 AM, Ingo Molnar <mingo@kernel.org> wrote:
> >
> > * Randy Dunlap <rdunlap@infradead.org> 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?
> >
> > I'd say let's delete the text. Mind sending a patch?
Yeah, all the distros are packaging those in some firmware-extra or
whatever package anyway.
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2013-11-07 12:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 5:44 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 [this message]
2013-11-07 8:43 ` Arkadiusz Miskiewicz
2013-11-07 9:03 ` Ingo Molnar
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=20131107121014.GB27116@x1.alien8.de \
--to=bp@alien8.de \
--cc=arjan@infradead.org \
--cc=arjanvandeven@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome