From: Christoph Hellwig <hch@infradead.org>
To: Stephen Cameron <smcameron@yahoo.com>
Cc: linux-kernel@vger.kernel.org, james.bottomley@steeleye.com,
mike.miller@hp.com, steve.cameron@hp.com
Subject: Re: [PATCH] Perverting cciss
Date: Sun, 8 Apr 2007 11:19:02 +0100 [thread overview]
Message-ID: <20070408101902.GA2275@infradead.org> (raw)
In-Reply-To: <438450.66991.qm@web33002.mail.mud.yahoo.com>
On Fri, Apr 06, 2007 at 10:07:52AM -0700, Stephen Cameron wrote:
> How about something like this:
> (Since my mailer is sure to wreck the patch, it can be found intact here:
> http://cciss.cvs.sourceforge.net/*checkout*/cciss/patches/kernel.org-2.6/cciss_sg_io_block_pc.patch?revision=1.1
Looks good except for some codingstyle nits:
> @@ -45,7 +45,7 @@
> #include <linux/blkdev.h>
> #include <linux/genhd.h>
> #include <linux/completion.h>
> -
> +#include <scsi/sg.h>
Please don't remove the empty line after the include statements.
> + case SG_IO: return scsi_cmd_ioctl(filep, disk, cmd, argp);
should be split into two lines for readability.
Also is there a reason you don't want to pass down the various
other ioctls scsi_cmd_ioctl can handle to it?
> + if (blk_pc_request(cmd->rq)) {
> + if (cmd->rq->sense) {
> + if (cmd->rq->sense_len > cmd->err_info->SenseLen)
> + cmd->rq->sense_len = cmd->err_info->SenseLen;
> + memcpy(cmd->rq->sense, cmd->err_info->SenseInfo, cmd->rq->sense_len);
> + } else
> + cmd->rq->sense_len = 0;
> + }
Please add some linebreaks so that lines don't grow longer than 80
characters.
next prev parent reply other threads:[~2007-04-08 10:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-06 17:07 [PATCH] Perverting cciss Stephen Cameron
2007-04-08 10:19 ` Christoph Hellwig [this message]
2007-04-08 16:26 ` Stephen Cameron
-- strict thread matches above, loose matches on Subject: below --
2007-04-05 9:58 Hannes Reinecke
2007-04-05 10:03 ` Christoph Hellwig
2007-04-05 14:09 ` James Bottomley
2007-04-05 14:37 ` Miller, Mike (OS Dev)
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=20070408101902.GA2275@infradead.org \
--to=hch@infradead.org \
--cc=james.bottomley@steeleye.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.miller@hp.com \
--cc=smcameron@yahoo.com \
--cc=steve.cameron@hp.com \
/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