From: David Miller <davem@davemloft.net>
To: matthew@wil.cx
Cc: sparclinux@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: slave_configure for qlogicpti
Date: Sun, 30 Sep 2007 17:29:52 -0700 (PDT) [thread overview]
Message-ID: <20070930.172952.85384131.davem@davemloft.net> (raw)
In-Reply-To: <20070919124637.GE7624@parisc-linux.org>
From: Matthew Wilcox <matthew@wil.cx>
Date: Wed, 19 Sep 2007 06:46:37 -0600
>
> I haven't even compile-tested this. But look how much ugly code it
> deletes if it works!
It compiles :-) You deleted the only uses of scsi_rbuf_{get,put}()
so you can kill those off too.
I don't have the time to setup things for testing this patch on
the qlogicpti hardware I have, but with the scsi_rbuf_{get,put}()
deletion added to the patch I would really like to see this go
into 2.6.24 anyways.
If things explode I'll pick up the pieces.
Acked-by: David S. Miller <davem@davemloft.net>
next prev parent reply other threads:[~2007-10-01 0:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 12:46 slave_configure for qlogicpti Matthew Wilcox
2007-10-01 0:29 ` David Miller [this message]
2007-10-01 0:52 ` Jeff Garzik
2007-10-01 1:24 ` David Miller
2007-10-01 12:22 ` 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=20070930.172952.85384131.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=sparclinux@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