linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Christoph Hellwig <hch@lst.de>,
	jejb@SteelEye.com, linux-scsi@vger.kernel.org,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] move ->eh_strategy_handler to the transport class
Date: Mon, 03 Apr 2006 06:44:50 -0400	[thread overview]
Message-ID: <4430FCA2.4070008@garzik.org> (raw)
In-Reply-To: <1143919437.3368.12.camel@mulgrave.il.steeleye.com>

James Bottomley wrote:
> On Sat, 2006-04-01 at 13:10 -0500, Jeff Garzik wrote:
>> I would prefer to merge it through the libata-dev queue, since -- as a 
>> glance through the recent kernel changelog shows -- Tejun Heo has been 
>> ripping through this part of libata as well.
> 
> I'm afraid we can't do that since we have the sas class to convert as
> well ... what I could do is take it through a separate tree and pull
> that into scsi-misc and you can pull it into libata.  That will
> (hopefully) ensure we both get it right.

Grumble!!  The following is why I wanted to merge it through libata:

Linus writes:
> Ok, 
>  it's two weeks since 2.6.16, and the merge window is closed.

This is precisely why I grumbled last time libata and scsi-misc needed 
some synchronization.  scsi-misc just isn't pushed as often as libata, 
and I'm stuck behind a slow-moving car.

I think Christoph's patch can still go into 2.6.17-rc I think.  I'll get 
that separate repository together if I don't hear from you soon.

	Jeff




      parent reply	other threads:[~2006-04-03 10:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060401172104.GA16921@lst.de>
2006-04-01 18:10 ` [PATCH] move ->eh_strategy_handler to the transport class Jeff Garzik
2006-04-01 19:23   ` James Bottomley
2006-04-01 19:27     ` Jeff Garzik
2006-04-03 10:44     ` Jeff Garzik [this message]

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=4430FCA2.4070008@garzik.org \
    --to=jeff@garzik.org \
    --cc=James.Bottomley@SteelEye.com \
    --cc=akpm@osdl.org \
    --cc=hch@lst.de \
    --cc=jejb@SteelEye.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.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 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).