LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Gadiyar, Anand" <gadiyar@ti.com>
To: Ed Tomlinson <edt@aei.ca>
Cc: Oliver Neukum <oneukum@suse.de>,
	linux-kernel@vger.kernel.org, linux-bluetooth@vger.kernel.org,
	linux-usb@vger.kernel.org
Subject: Re: [BUG] usb problems in .38-rc3+
Date: Tue, 8 Feb 2011 12:16:16 +0530	[thread overview]
Message-ID: <AANLkTinpKwe2vWH3=Ur+N76a6KyfuFp0V-EznXXS7m+p@mail.gmail.com> (raw)
In-Reply-To: <201102072115.20858.edt@aei.ca>

On Tue, Feb 8, 2011 at 7:45 AM, Ed Tomlinson <edt@aei.ca> wrote:
> I tried bisecting without much luck.  It started with about 4000 commits to check.  It was still bad
> when it reached the first 1000 commits post .37.  Then all boots started crashing.  I think its possible
> to restrict a bisect to a directory - if so, what dir should I try?
>

Maybe drivers/ or drivers/usb would be enough for a first attempt?
I usually start there.

You could just do:

git bisect start -- [path]

to restrict bisection to commits that touch [path].

- Anand

  reply	other threads:[~2011-02-08  6:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-05 19:17 [BUG] usb problems in .38-rc3+ Ed Tomlinson
2011-02-05 20:16 ` Alan Stern
2011-02-05 22:50   ` Przemo Firszt
2011-02-06  4:27   ` Ed Tomlinson
2011-02-07  9:09 ` Oliver Neukum
2011-02-08  0:20   ` Ed Tomlinson
2011-02-08  2:15     ` Ed Tomlinson
2011-02-08  6:46       ` Gadiyar, Anand [this message]
2011-02-09  4:31         ` Ed Tomlinson
2011-02-09  6:17           ` Anand Gadiyar
2011-02-09 23:48             ` Ed Tomlinson
2011-02-12 14:38             ` Ed Tomlinson
2011-02-16 14:00 ` Gustavo F. Padovan
2011-02-16 18:38   ` Ed Tomlinson
2011-02-16 18:47     ` Gustavo F. Padovan
     [not found]       ` <201102201209.20799.edt@aei.ca>
2011-02-20 20:49         ` Ed Tomlinson

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='AANLkTinpKwe2vWH3=Ur+N76a6KyfuFp0V-EznXXS7m+p@mail.gmail.com' \
    --to=gadiyar@ti.com \
    --cc=edt@aei.ca \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.de \
    /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;
as well as URLs for NNTP newsgroup(s).