From: Ingo Molnar <mingo@elte.hu>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Dave Jones <davej@redhat.com>, Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, Mike Galbraith <efault@gmx.de>,
Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
Len Brown <len.brown@intel.com>,
Zhao Yakui <yakui.zhao@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/7] use smp_call_function_single() in arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.c
Date: Tue, 14 Apr 2009 13:06:10 +0200 [thread overview]
Message-ID: <20090414110610.GO3558@elte.hu> (raw)
In-Reply-To: <200904141835.41961.rusty@rustcorp.com.au>
* Rusty Russell <rusty@rustcorp.com.au> wrote:
> On Mon, 13 Apr 2009 09:46:57 am Dave Jones wrote:
> > On Mon, Apr 13, 2009 at 09:30:02AM +0930, Rusty Russell wrote:
> > > From: Andrew Morton <akpm@linux-foundation.org>
> > >
> > > Impact: fix sysbench(oltp)+mysql 10% regression with 2.6.30-rc1
> > >
> >
> > This, and the other cpufreq related patches in this series look
> > sound to me. Given the other non-cpufreq bits in the series, do
> > you want to just have these go through Andrew and onto Linus?
>
> Sure, that's certainly easiest for me. I'd assumed Ingo would
> snarf them, but as he's suggested -mm, Andrew?
I tend to let the snarfing be done by the tree which introduced a
regression to begin with ;-)
Ingo
prev parent reply other threads:[~2009-04-14 11:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 0:00 [PATCH 1/7] use smp_call_function_single() in arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.c Rusty Russell
2009-04-13 0:16 ` Dave Jones
2009-04-13 3:40 ` Ingo Molnar
2009-04-14 9:05 ` Rusty Russell
2009-04-14 11:06 ` Ingo Molnar [this message]
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=20090414110610.GO3558@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=davej@redhat.com \
--cc=efault@gmx.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@intel.com \
--cc=yakui.zhao@intel.com \
/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