From: Boaz Harrosh <bharrosh@panasas.com>
To: "James Bottomley" <James.Bottomley@SteelEye.com>,
"Christoph Hellwig" <hch@lst.de>,
"\"Jürgen E. Fischer\"" <fischer@norbit.de>,
"FUJITA Tomonori" <fujita.tomonori@lab.ntt.co.jp>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [patch 0/4] aha152x.c - Cleanup, need help in testing and auditing
Date: Thu, 12 Jul 2007 16:17:58 +0300 [thread overview]
Message-ID: <46962A06.3060500@panasas.com> (raw)
In-Reply-To: <4695F76F.5000305@panasas.com>
Boaz Harrosh wrote:
> In motivation for the !use_sg cleanup and use of accessors
> I needed to do some restructuring of the aha152x.c driver.
>
> I have tried to be as careful as I could, but with out
> the hardware for testing, it is hard. Christoph and James
> You are signed on a couple of the last patches to this driver
> So you are probably somewhat familiar with the code. Could
> you please review the patchset to see that nothing is broken.
>
> If any one has an Hardware that uses aha152x.c, please help me
> with testing this patchset. If it does not work could you please
> do a short bisect of which patch breaks out of the 4.
>
> The problematic parts were that the driver writes all over the
> scsi_cmnd members in couple of places. To untangle that I divided
> the work to stages for easier review and testing. I was very
> verbose at each patch explanation, mainly for myself to try and
> prove that the changes are sound.
>
> [patch 1/4] aha152x.c - Preliminary fixes and comments
> Some weird typos and some hard coded numbers made the code
> very hard to understand.
>
> [patch 2/4] aha152x.c - Clean Reset path
> On the Reset code path the driver would save, write, than
> restore scsi_cmnd members. Here I propose a solution that
> does not need to do that.
>
> [patch 3/4] aha152x.c - Fix check_condition code-path
> In case of a Status return from a target. The driver
> would re-queue the command with a REQUEST_SENSE read.
> Again save, write, restore. I cleaned that up to a stage
> I can be happy with. Also while at it I fixed a BUG with
> "resid".
>
> [patch 4/4] aha152x.c - use data accessors and !use_sg cleanup
> And now everything is ready for this one.
>
> Thanks for any help
> Boaz
Ooff I forgot to:
Signed-off-by: Boaz Harrosh <bharrosh@panasas.com>
all of these patches.
next prev parent reply other threads:[~2007-07-12 13:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 9:42 [patch 0/4] aha152x.c - Cleanup, need help in testing and auditing Boaz Harrosh
2007-07-12 9:49 ` [patch 1/4] aha152x.c - Preliminary fixes and some comments Boaz Harrosh
2007-07-12 9:55 ` [patch 2/4] aha152x.c - Clean Reset path Boaz Harrosh
2007-07-12 10:05 ` [patch 3/4] aha152x.c - Fix check_condition code-path Boaz Harrosh
2007-07-12 10:09 ` [patch 4/4] aha152x.c - use data accessors and !use_sg cleanup Boaz Harrosh
2007-07-12 13:17 ` Boaz Harrosh [this message]
2007-07-12 20:57 ` [patch 0/4] aha152x.c - Cleanup, need help in testing and auditing Randy Dunlap
2007-07-16 9:22 ` Boaz Harrosh
2007-07-16 9:35 ` Christoph Hellwig
2007-07-18 0:16 ` Randy Dunlap
2007-07-18 9:29 ` Boaz Harrosh
2007-07-18 12:39 ` Boaz Harrosh
2007-07-18 17:33 ` Randy Dunlap
2007-07-18 21:58 ` Randy Dunlap
2007-07-19 2:43 ` Randy Dunlap
2007-07-19 3:03 ` Randy Dunlap
2007-07-19 13:04 ` Boaz Harrosh
2007-07-19 15:37 ` Randy Dunlap
2007-07-19 15:57 ` Boaz Harrosh
2007-07-19 17:49 ` Randy Dunlap
2007-07-24 10:12 ` Boaz Harrosh
2007-07-24 16:17 ` Randy Dunlap
2007-08-16 5:22 ` Randy Dunlap
2007-08-16 14:39 ` James Bottomley
2007-08-16 17:20 ` Randy Dunlap
2007-08-16 17:18 ` James Bottomley
2007-08-17 19:59 ` Randy Dunlap
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=46962A06.3060500@panasas.com \
--to=bharrosh@panasas.com \
--cc=James.Bottomley@SteelEye.com \
--cc=fischer@norbit.de \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hch@lst.de \
--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 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.