All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Sander <sander@humilis.net>, Mark Lord <liml@rtr.ca>,
	Mark Lord <lkml@rtr.ca>, Andrew Morton <akpm@osdl.org>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.6.xx: sata_mv: another critical fix
Date: Tue, 21 Mar 2006 16:09:21 -0500	[thread overview]
Message-ID: <44206B81.1030309@garzik.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0603211249270.3622@g5.osdl.org>

Linus Torvalds wrote:
> 
> On Tue, 21 Mar 2006, Sander wrote:
> 
>>Is there a quick patch to suspect, or should I narrow down some more per
>>Andrew's instructions?
> 
> 
> Well, the only thing that changes the sata_mv driver in the -mm1 patchset 
> is the "git-libata-all.patch" patch, so you might start out just applying 
> that one broken-out patch and verifying that it fixes things for you.
> 
> That's git commit 2086a4aa2b41846801fad01f0fb1723134865ebb from Jeff's 
> libata tree.
> 
> At that point, if that fixes it for you, you'd be best off bisecting it in 
> Jeff's libata tree using git, to figure out what it is that fixed things. 
> Jeff?

There were a bunch of sata_mv fixes in git-libata-all, all of which are 
actually now in your linux-2.6.git tree.  This latest libata push gets 
sata_mv working on my 6042 card, and in the process fixes several bugs I 
found while doing the 6042 work.

Post-pull, git-libata-all is down to just a few development patches, 
none of which involve sata_mv.

In any case, one could be lazy, and simply bisect the main tree (and/or 
simply verify that the problem is gone in 2.6.16-git<today>).

	Jeff

  reply	other threads:[~2006-03-21 21:09 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-21  0:57 [git patch append] sata_mv fix Jeff Garzik
2006-03-21  5:00 ` [PATCH] 2.6.xx: sata_mv: another critical fix Mark Lord
2006-03-21 12:13   ` Sander
2006-03-21 13:51     ` Mark Lord
2006-03-21 15:37       ` Sander
2006-03-21 18:33         ` Linus Torvalds
2006-03-21 19:15           ` Sander
2006-03-21 19:22             ` Mark Lord
2006-03-21 19:35             ` Linus Torvalds
2006-03-21 20:44               ` Sander
2006-03-21 20:59                 ` Linus Torvalds
2006-03-21 21:09                   ` Jeff Garzik [this message]
2006-03-21 21:19                     ` Linus Torvalds
2006-03-21 21:37                       ` Jeff Garzik
2006-03-22  5:48                         ` Sander
2006-03-22  9:00                       ` Sander
2006-03-22 14:50                         ` Mark Lord
2006-03-22 17:09                           ` Sander
2006-03-22 17:53                             ` Eric D. Mudama
2006-03-22 18:01                               ` Sander
2006-03-22 17:55                             ` Mark Lord
2006-03-28  4:34                             ` Mark Lord
2006-05-03 12:16                               ` Sander
2006-05-03 12:42                                 ` Mark Lord
2006-05-03 13:32                                   ` Sander
2006-05-03 16:46                                     ` Mark Lord
2006-05-03 18:39                                       ` Sander
2006-03-22  2:12   ` Jeff Garzik

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=44206B81.1030309@garzik.org \
    --to=jeff@garzik.org \
    --cc=akpm@osdl.org \
    --cc=liml@rtr.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@rtr.ca \
    --cc=sander@humilis.net \
    --cc=torvalds@osdl.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.