From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org, mingo@kernel.org,
Aravind.Gopalakrishnan@amd.com, tglx@linutronix.de, bp@suse.de,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/microcode] x86, microcode: Move to a proper location
Date: Tue, 14 Jan 2014 08:10:28 -0800 [thread overview]
Message-ID: <52D56174.9010608@zytor.com> (raw)
In-Reply-To: <tip-bad5fa631fca5466401cd4a48e30cc1f1cb6101e@git.kernel.org>
On 01/14/2014 05:58 AM, tip-bot for Borislav Petkov wrote:
> Commit-ID: bad5fa631fca5466401cd4a48e30cc1f1cb6101e
> Gitweb: http://git.kernel.org/tip/bad5fa631fca5466401cd4a48e30cc1f1cb6101e
> Author: Borislav Petkov <bp@suse.de>
> AuthorDate: Sun, 1 Dec 2013 18:09:58 +0100
> Committer: Borislav Petkov <bp@suse.de>
> CommitDate: Mon, 13 Jan 2014 20:00:12 +0100
>
> x86, microcode: Move to a proper location
>
> We've grown a bunch of microcode loader files all prefixed with
> "microcode_". They should be under cpu/ because this is strictly
> CPU-related functionality so do that and drop the prefix since they're
> in their own directory now which gives that prefix. :)
>
> While at it, drop MICROCODE_INTEL_LIB config item and stash the
> functionality under CONFIG_MICROCODE_INTEL as it was its only user.
>
Quite frankly I would be much happier if we didn't stash so much under
arch/x86/kernel/cpu ... quite frankly it feels like almost *anything*
could go under there. The microcode code, for example, could go under
its own subtree.
Both kernel and kernel/cpu really could use a house cleaning and
actually separate things out into better categories and avoid needlessly
deep pathnames.
-hpa
next parent reply other threads:[~2014-01-14 16:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-bad5fa631fca5466401cd4a48e30cc1f1cb6101e@git.kernel.org>
2014-01-14 16:10 ` H. Peter Anvin [this message]
2014-01-14 16:22 ` [tip:x86/microcode] x86, microcode: Move to a proper location Ingo Molnar
2014-01-14 16:36 ` Borislav Petkov
2014-01-14 16:39 ` H. Peter Anvin
2014-01-14 17:38 ` Ingo Molnar
2014-01-14 18:58 ` Borislav Petkov
2014-01-14 19:18 ` H. Peter Anvin
2014-01-14 19:27 ` Borislav Petkov
2014-01-14 19:32 ` H. Peter Anvin
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=52D56174.9010608@zytor.com \
--to=hpa@zytor.com \
--cc=Aravind.Gopalakrishnan@amd.com \
--cc=bp@suse.de \
--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 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.