From: Ingo Molnar <mingo@kernel.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Borislav Petkov <bp@alien8.de>,
linux-kernel@vger.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 18:38:27 +0100 [thread overview]
Message-ID: <20140114173827.GA2679@gmail.com> (raw)
In-Reply-To: <52D56856.9050201@zytor.com>
* H. Peter Anvin <hpa@zytor.com> wrote:
> On 01/14/2014 08:36 AM, Borislav Petkov wrote:
> > On Tue, Jan 14, 2014 at 05:22:03PM +0100, Ingo Molnar wrote:
> >> Absolutely. I think moving arch/x86/kernel/cpu/ to arch/x86/cpu/
> >> would be a first good step. It's all kernel code, there's other
> >> subdirectories there that are kernel code ('pci/', 'platform/', etc.),
> >> so there's little point in continuing the historic accident of a
> >> 'kernel/' subdirectory.
> >>
> >> Once that is done we can move certain things outside as well - for
> >> example arch/x86/cpu/perf/ could probably move to arch/x86/events/,
> >> because that code is not about CPU events anymore either.
> >
> > All fine and dandy with me, but I'd prefer to do this after the merge
> > window, i.e. for 3.15. Rushing it now would just cause unnecessary
> > trouble IMO.
> >
>
> Oh, absolutely.
Agreed.
Thanks,
Ingo
next prev parent reply other threads:[~2014-01-14 17:38 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 ` [tip:x86/microcode] x86, microcode: Move to a proper location H. Peter Anvin
2014-01-14 16:22 ` Ingo Molnar
2014-01-14 16:36 ` Borislav Petkov
2014-01-14 16:39 ` H. Peter Anvin
2014-01-14 17:38 ` Ingo Molnar [this message]
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=20140114173827.GA2679@gmail.com \
--to=mingo@kernel.org \
--cc=Aravind.Gopalakrishnan@amd.com \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.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