public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Thomas Renninger <trenn@suse.de>,
	Ben Hutchings <ben@decadent.org.uk>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	x86@kernel.org, Andi Kleen <ak@linux.intel.com>,
	linux-kernel@vger.kernel.org, Len Brown <lenb@kernel.org>,
	linux-pm@vger.kernel.org, Dave Jones <davej@redhat.com>,
	cpufreq@vger.kernel.org
Subject: Re: [PATCH 0/5] Clean up x86 CPU auto-loading
Date: Sun, 12 Feb 2012 19:00:31 -0800	[thread overview]
Message-ID: <4F387CCF.7040604@zytor.com> (raw)
In-Reply-To: <20120213021847.GA25382@kroah.com>

On 02/12/2012 06:18 PM, Greg KH wrote:
> I can take them, unless the x86 maintainers object and want to take them
> through their tree.

Why don't we take them... I think it makes more sense long-term.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


  reply	other threads:[~2012-02-13  3:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-11 22:44 [PATCH 0/5] Clean up x86 CPU auto-loading Ben Hutchings
2012-02-11 22:46 ` [PATCH 1/5] x86/cpu: Fix overrun check in arch_print_cpu_modalias() Ben Hutchings
2012-02-11 22:52 ` [PATCH 2/5] x86/cpu: Clean up modalias feature matching Ben Hutchings
2012-02-11 22:54 ` [PATCH 3/5] intel_idle: Fix ID for Nehalem-EX Xeon in device ID table Ben Hutchings
2012-02-11 22:55 ` [PATCH 4/5] intel_idle: Revert change of auto_demotion_flags for Nehalem Ben Hutchings
2012-02-12 17:10   ` Thomas Renninger
2012-02-11 22:55 ` [PATCH 5/5] powernow-k7: Fix CPU family number Ben Hutchings
2012-02-12 23:10 ` [PATCH 0/5] Clean up x86 CPU auto-loading Thomas Renninger
2012-02-13  1:26   ` H. Peter Anvin
2012-02-13 22:26     ` Greg KH
2012-02-13 22:55       ` H. Peter Anvin
2012-02-13  2:18   ` Greg KH
2012-02-13  3:00     ` H. Peter Anvin [this message]
2012-02-13  6:43       ` Greg KH

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=4F387CCF.7040604@zytor.com \
    --to=hpa@zytor.com \
    --cc=ak@linux.intel.com \
    --cc=ben@decadent.org.uk \
    --cc=cpufreq@vger.kernel.org \
    --cc=davej@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=trenn@suse.de \
    --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