From: Boaz Harrosh <bharrosh@panasas.com>
To: "James Bottomley" <James.Bottomley@SteelEye.com>,
"\"Jürgen E. Fischer\"" <fischer@norbit.de>,
"FUJITA Tomonori" <fujita.tomonori@lab.ntt.co.jp>,
linux-scsi <linux-scsi@vger.kernel.org>,
"Randy Dunlap" <rdunlap@xenotime.net>
Subject: [patch 0/6] aha152x.c - Cleanup, bugfixes, convert to accessors
Date: Sun, 29 Jul 2007 22:10:39 +0300 [thread overview]
Message-ID: <46ACE62F.4070108@panasas.com> (raw)
In motivation for the !use_sg cleanup and use of accessors
I needed to do some restructuring of the aha152x.c driver.
The patchset has been tested by Randy Dunlap on a PCMCIA
hardware based on aha152x.c. And some bugs where fixed
in the process by Randy.
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/6] aha152x in debug mode
Enabling debug prints would not compile...
[patch 2/6] aha152x.c - use bounce buffer
Override .slave_alloc() to force use of a bounce buffer
This fixes a kernel crash with HIGHMEM=y configs.
[patch 3/6] aha152x.c - Preliminary fixes and comments
Some weird typos and some hard coded numbers made the code
very hard to understand.
[patch 4/6] 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 5/6] 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 6/6] aha152x.c - use data accessors and !use_sg cleanup
And now everything is ready for this one.
Jams I am not getting any response from Jürgen E. Fischer which
is to my understanding the maintainer of this driver. With Randy's
testing review, could we accept these changes?
Boaz
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2007-07-29 19:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-29 19:10 Boaz Harrosh [this message]
2007-07-29 19:16 ` [PATCH 1/6] aha152x.c - In debug mode Boaz Harrosh
2007-07-29 19:18 ` [PATCH 2/6] aha152x.c - use bounce buffer Boaz Harrosh
2007-07-29 19:22 ` [PATCH 3/6] aha152x.c - Preliminary fixes and some comments Boaz Harrosh
2007-07-29 19:24 ` [PATCH 4/6] aha152x.c - Clean Reset path Boaz Harrosh
2007-07-29 19:27 ` [PATCH 5/6] aha152x.c - Fix check_condition code-path Boaz Harrosh
2007-07-31 0:13 ` Randy Dunlap
2007-07-31 7:59 ` Boaz Harrosh
2007-07-31 17:08 ` Randy Dunlap
2007-07-31 18:40 ` Randy Dunlap
2007-08-01 13:51 ` James Bottomley
2007-08-01 16:34 ` Randy Dunlap
2007-08-02 11:26 ` Boaz Harrosh
2007-08-02 19:09 ` Randy Dunlap
2007-08-02 19:08 ` James Bottomley
2007-08-02 20:22 ` Jürgen E. Fischer
2007-08-02 22:47 ` Randy Dunlap
2007-07-29 19:29 ` [PATCH 6/6] aha152x.c - use data accessors and !use_sg cleanup Boaz Harrosh
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=46ACE62F.4070108@panasas.com \
--to=bharrosh@panasas.com \
--cc=James.Bottomley@SteelEye.com \
--cc=fischer@norbit.de \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-scsi@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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.