From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Martin Rogge <marogge@onlinehome.de>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Mark Lord <liml@rtr.ca>,
linux-ide@vger.kernel.org
Subject: Re: Fwd: CMD 64x regression from 2.6.21 to 2.6.22 and 2.6.23?
Date: Thu, 18 Oct 2007 00:40:21 +0400 [thread overview]
Message-ID: <47167335.1020903@ru.mvista.com> (raw)
In-Reply-To: <200710172115.13068.marogge@onlinehome.de>
Hello.
Martin Rogge wrote:
>>Martin, could you run git-bisect (http://kerneltrap.org/node/11753 - sorry
>>for not explaining the procudure myself but Linus did it really well)
>>starting with:
>> git bisect good 688a87d145e04f6761c63e7f2e19fd9b3e4ca060
>> git bisect bad 826a1b6502d0d1d67fc41043fc831e90f2ef5835
>>The "good" one is the last commit before cmd64x changes and the "bad" one
>>is the first commit after them. Since there is only 5 commits in between
>>it should be really quick find the bad one (worst-case: 3
>>recompiles/reboots).
>
>
> I'll do my best. I appear to have git 1.5.2.2 on my machine, but I've never
> used it. In the old days we used not to have such luxury!
> Give me a few days. I shall report back.
BTW, can you try adding #define DEBUG to the driver meanwhile?..
> cu Martin
WBR, Sergei
next prev parent reply other threads:[~2007-10-17 20:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200710142211.03382.marogge@onlinehome.de>
2007-10-15 17:14 ` Fwd: CMD 64x regression from 2.6.21 to 2.6.22 and 2.6.23? Sergei Shtylyov
[not found] ` <200710152339.33718.marogge@onlinehome.de>
2007-10-16 11:53 ` Sergei Shtylyov
2007-10-16 12:43 ` Mark Lord
2007-10-16 12:59 ` Sergei Shtylyov
2007-10-16 22:14 ` Bartlomiej Zolnierkiewicz
2007-10-17 19:15 ` Martin Rogge
2007-10-17 20:40 ` Sergei Shtylyov [this message]
2007-10-19 19:58 ` Martin Rogge
2007-10-19 20:26 ` Sergei Shtylyov
2007-10-19 23:09 ` Martin Rogge
2007-10-20 14:55 ` Sergei Shtylyov
2007-10-20 17:11 ` Sergei Shtylyov
2007-10-21 20:55 ` Martin Rogge
2007-10-26 15:38 ` Sergei Shtylyov
2007-10-18 22:39 ` Martin Rogge
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=47167335.1020903@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=bzolnier@gmail.com \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=marogge@onlinehome.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).