public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Mike Galbraith <efault@gmx.de>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: x86-tip: cpufreq breakage	-	bisection	fingers	89c9215165ca609096e845926d9a18f1306176a4
Date: Thu, 05 Mar 2009 13:36:28 +0900	[thread overview]
Message-ID: <49AF56CC.6020307@kernel.org> (raw)
In-Reply-To: <1236177327.6001.2.camel@marge.simson.net>

Mike Galbraith wrote:
> On Wed, 2009-03-04 at 22:58 +0900, Tejun Heo wrote:
>> Mike Galbraith wrote:
>>> On Wed, 2009-03-04 at 18:43 +0900, Tejun Heo wrote:
>>>> Tejun Heo wrote:
>>>>> I've used the config file you attached and the commit ID I used is
>>>>> d0c4f570276cb4d2dc4215b90eb7cb6e2bdd4a15.
>>> My tip tree is at v2.6.29-rc6-2441-g4239438.
>> Eh... how do I map that to git commit?
> 
> The last 6, short form of 4239438b08fe8ec149ddc530238ca131bf88d290.

Okay, got it.  It's slightly convoluted and can possibly affect other
allocation methods too.  I'll report back after trying a few things.

Thanks.

-- 
tejun

  parent reply	other threads:[~2009-03-05  4:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03 13:07 x86-tip: cpufreq breakage - bisection fingers 89c9215165ca609096e845926d9a18f1306176a4 Mike Galbraith
2009-03-03 14:31 ` Ingo Molnar
2009-03-03 16:38   ` Mike Galbraith
2009-03-04  1:59     ` Tejun Heo
2009-03-04  3:43       ` Mike Galbraith
2009-03-04  6:14         ` Mike Galbraith
2009-03-04  6:31           ` Tejun Heo
2009-03-04  9:38             ` Tejun Heo
2009-03-04  9:43               ` Tejun Heo
2009-03-04 10:44                 ` Mike Galbraith
2009-03-04 13:58                   ` Tejun Heo
2009-03-04 14:35                     ` Mike Galbraith
2009-03-04 14:40                       ` Mike Galbraith
2009-03-04 17:08                       ` Ingo Molnar
2009-03-05  4:36                       ` Tejun Heo [this message]
2009-03-04 12:13               ` Mike Galbraith

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=49AF56CC.6020307@kernel.org \
    --to=tj@kernel.org \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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