[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <29495f1d0705291006o1f812ce2n25fa962c222e0b45@mail.gmail.com>
Date: Tue, 29 May 2007 10:06:16 -0700
From: "Nish Aravamudan" <nish.aravamudan@...il.com>
To: "Mark Lord" <lkml@....ca>
Cc: "Linus Torvalds" <torvalds@...ux-foundation.org>,
"Linux Kernel" <linux-kernel@...r.kernel.org>,
"Greg KH" <gregkh@...e.de>,
"Andrew Morton" <akpm@...ux-foundation.org>
Subject: Re: Regression: USB is nfg after suspend/resume(RAM) cycle on Intel chipset
On 5/29/07, Mark Lord <lkml@....ca> wrote:
> Linus Torvalds wrote:
> >
> > On Tue, 29 May 2007, Mark Lord wrote:
> >> There are a zillion USB patches in 2.6.22-rc*.
> >> Greg: got any good suggestions on which one to revert first?
> >
> > Any chance of bisecting it?
>
> Ugh. Is there a way to tell bisect to only work around the USB updates?
> I suppose so.. just pick the commits before and after the USB dump
> and let it pick through the middle.
git bisect start drivers/usb ? Should only bisect over commits
affecting any paths you give it.
> Still, that'll take a few hours, and frankly I'm getting sick of having
> to re-debug the USB layer with each new kernel rev.
>
> Got a pointer to the "bisect how-to" ?
The man-page is pretty good. There used to be
http://www.kernel.org/pub/software/scm/git/docs/howto/isolate-bugs-with-bisect.txt,
but it's 404 now...
Thanks,
Nish
-
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/
Powered by blists - more mailing lists