linux-kernel - Re: [BUG] usb problems in .38-rc3+

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <AANLkTinpKwe2vWH3=Ur+N76a6KyfuFp0V-EznXXS7m+p@mail.gmail.com>
Date:	Tue, 8 Feb 2011 12:16:16 +0530
From:	"Gadiyar, Anand" <gadiyar@...com>
To:	Ed Tomlinson <edt@....ca>
Cc:	Oliver Neukum <oneukum@...e.de>, linux-kernel@...r.kernel.org,
	linux-bluetooth@...r.kernel.org, linux-usb@...r.kernel.org
Subject: Re: [BUG] usb problems in .38-rc3+

On Tue, Feb 8, 2011 at 7:45 AM, Ed Tomlinson <edt@....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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/