From: john cooper <john.cooper@third-harmonic.com>
To: Daniel Walker <dwalker@mvista.com>
Cc: Tim Bird <tim.bird@am.sony.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
dirk.behme@googlemail.com,
linux kernel <linux-kernel@vger.kernel.org>,
john cooper <john.cooper@third-harmonic.com>
Subject: Re: Need help debugging RT-preempt patch
Date: Mon, 07 May 2007 20:20:28 -0400 [thread overview]
Message-ID: <463FC24C.309@third-harmonic.com> (raw)
In-Reply-To: <1178572299.3164.14.camel@imap.mvista.com>
Daniel Walker wrote:
> I'm not sure I'd get into "bisecting" one big patch. Especially if you
> new to the patches inner workings..
>
> You can bisect by kernel version using the older patches but it's
> clearly limited,
>
> http://people.redhat.com/mingo/realtime-preempt/older/
Actually working on this more closely over a year or so ago I
found a binary chop among patch versions to often be the
fastest means of locating the source of breakage. Though that
may have been more applicable when several patch versions per
day were being generated.
-john
--
john.cooper@third-harmonic.com
prev parent reply other threads:[~2007-05-08 1:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-07 18:47 Need help debugging RT-preempt patch Tim Bird
2007-05-07 20:28 ` Daniel Walker
2007-05-07 21:02 ` Tim Bird
2007-05-07 21:11 ` Daniel Walker
2007-05-08 0:20 ` john cooper [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=463FC24C.309@third-harmonic.com \
--to=john.cooper@third-harmonic.com \
--cc=dirk.behme@googlemail.com \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tim.bird@am.sony.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