From: Bill Davidsen <davidsen@tmr.com>
To: Greg Lee <glee@swspec.com>, linux-kernel@vger.kernel.org
Subject: Re: HZ != 1000 causes problem with serial device shown by git-bisect
Date: Wed, 29 Mar 2006 12:22:32 -0500 [thread overview]
Message-ID: <442AC258.6010804@tmr.com> (raw)
In-Reply-To: <20060328081324.GA15222@flint.arm.linux.org.uk>
Russell King wrote:
> On Mon, Mar 27, 2006 at 06:46:02PM -0500, Greg Lee wrote:
>> I have also tried a number of other kernels and the problem exists all
>> the way to 2.6.15.6 but is fixed in 2.6.16, so I am going to git-bisect
>> 2.6.15.6 to 2.6.16, but I thought I would get this message out now in
>> case someone has an inkling of what the problem is.
>
> Saying that the problem is between 2.6.15.6 and 2.6.16 is rather
> meaningless because you're effectively omitting _all_ the development
> work between 2.6.15 to 2.6.16, and that's likely where the problem
> lies. Hence, you're omitting all the 2.6.16-rc kernels from your
> testing.
But won't a git bisect cover all the bases even so? Aren't rc versions
just selected git pulls?
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next prev parent reply other threads:[~2006-03-30 20:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-27 23:46 HZ != 1000 causes problem with serial device shown by git-bisect Greg Lee
2006-03-28 1:27 ` Lee Revell
2006-03-28 2:03 ` HZ != 1000 causes problem with serial device shown bygit-bisect Greg Lee
2006-03-28 2:19 ` Alistair John Strachan
2006-03-28 5:37 ` HZ != 1000 causes problem with serial device shown by git-bisect Valdis.Kletnieks
2006-03-28 13:44 ` Greg Lee
2006-03-28 8:13 ` Russell King
2006-03-28 14:17 ` Greg Lee
2006-03-29 17:22 ` Bill Davidsen [this message]
2006-03-28 14:13 ` Alan Cox
2006-03-29 17:31 ` Bill Davidsen
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=442AC258.6010804@tmr.com \
--to=davidsen@tmr.com \
--cc=glee@swspec.com \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.