linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Christoph Hellwig <hch@infradead.org>,
	Jeff Garzik <jeff@garzik.org>,
	James Bottomley <James.Bottomley@SteelEye.com>,
	linux-scsi@vger.kernel.org, achim_leubner@adaptec.com,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/4] more gdth patches for your amusement
Date: Tue, 25 Sep 2007 14:17:44 +0200	[thread overview]
Message-ID: <46F8FC68.4020002@panasas.com> (raw)
In-Reply-To: <20070925115608.GR10625@parisc-linux.org>

On Tue, Sep 25 2007 at 13:56 +0200, Matthew Wilcox <matthew@wil.cx> wrote:
> On Tue, Sep 25, 2007 at 11:51:13AM +0200, Boaz Harrosh wrote:
>> On top of that I have my own agenda of cleaning the !use_sg code paths and getting
>> rid of scsi_cmnd abuse, so there is also that.
> 
> This seems like a good time to post my own patch that removes the use of
> ->scsi_done from gdth.  I have a plan to remove the ->scsi_done() callback
> (drivers will simply call the scsi_done() function directly), and fixing
> the half-dozen drivers that override it is part of that.
> 
> I haven't looked at Christoph's, Jeff's or your patches yet, so this
> patch may be entirely worthless.  My goal with it was not to clean up
> the driver (though it does a little), but to get gdth out of the way of
> cleaning up scsi_cmnd.
> 
> commit 06142e2394d83929b8b25feab70caab47ddfb791
> Author: Matthew Wilcox <willy@linux.intel.com>
> Date:   Sat Sep 22 22:57:06 2007 -0400
> 
>     gdth: Make one abuse of scsi_cmnd less obvious
>     
>     Rather than having internal commands abuse scsi_done to call
>     gdth_scsi_done, have all the places that use to call scsi_done directly
>     call gdth_scsi_done, which now checks whether the command was internal,
>     and calls scsi_done if not.
>     
>     Signed-off-by: Matthew Wilcox <willy@linux.intel.com>
> 
> diff --git a/drivers/scsi/gdth.c b/drivers/scsi/gdth.c
> index b20c188..8a6a5f8 100644
> --- 

Hi Matthew!
This patch looks grate, Thanks. It is very good for the direction
I'm going to. However it does have a smallish conflict with One
of Jeff's patches where he completely removes the 2.4.x support.

If it is OK with you I will add your patch to my patchset with your
Singed-off-by, minus the conflict?
 
Boaz

  reply	other threads:[~2007-09-25 12:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-21 20:34 [PATCH 0/4] more gdth patches for your amusement Jeff Garzik
2007-07-21 20:34 ` [PATCH 1/4] gdth: kill gdth_{read,write}[bwl] wrappers Jeff Garzik
2007-07-21 20:35 ` [PATCH 2/4] gdth: Move probe-time error handling code to end of each function Jeff Garzik
2007-07-21 20:35 ` [PATCH 3/4] gdth: make some virt ctrlr code common; shuffle SHT members Jeff Garzik
2007-07-21 20:36 ` [PATCH 4/4] gdth: convert to modern SCSI host alloc/scan Jeff Garzik
2007-07-21 20:38 ` [PATCH 0/4] more gdth patches for your amusement Jeff Garzik
2007-09-15 14:12 ` James Bottomley
2007-09-25  0:25   ` Jeff Garzik
2007-09-25  8:20     ` Christoph Hellwig
2007-09-25  9:51       ` Boaz Harrosh
2007-09-25 11:56         ` Matthew Wilcox
2007-09-25 12:17           ` Boaz Harrosh [this message]
2007-09-25 12:22             ` Matthew Wilcox

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=46F8FC68.4020002@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=achim_leubner@adaptec.com \
    --cc=akpm@linux-foundation.org \
    --cc=hch@infradead.org \
    --cc=jeff@garzik.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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).