public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Greg Lee" <glee@swspec.com>
To: "'Russell King'" <rmk+lkml@arm.linux.org.uk>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: HZ != 1000 causes problem with serial device shown by git-bisect
Date: Tue, 28 Mar 2006 09:17:16 -0500	[thread overview]
Message-ID: <0f1401c65272$515bfc10$a100a8c0@casabyte.com> (raw)
In-Reply-To: <20060328081324.GA15222@flint.arm.linux.org.uk>

> 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.

Yes, I realized last night that the -rc kernels actually came before the 2.6.16.  I'm in
the process of a git-bisect between 2.6.15 and 2.6.16 which will cover all of the changes
made in the -rc kernels, right?

Greg



  reply	other threads:[~2006-03-28 14:19 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 [this message]
2006-03-29 17:22   ` Bill Davidsen
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='0f1401c65272$515bfc10$a100a8c0@casabyte.com' \
    --to=glee@swspec.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    /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