From: Jeff Garzik <jeff@garzik.org>
To: Gilbert Wu <Gilbert_Wu@adaptec.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi: Update Aic94xx SAS/SATA Linux open source device
Date: Fri, 31 Aug 2007 14:27:48 -0400 [thread overview]
Message-ID: <46D85DA4.1070008@garzik.org> (raw)
In-Reply-To: <1188583419.6353.9.camel@linux.site>
Gilbert Wu wrote:
> Subject: [PATCH] scsi: Update Aic94xx SAS/SATA Linux open source device
> driver to fix smartctl utility problem.
>
> Contribution:
> Gilbert Wu <gilbert_wu@adaptec.com>
>
> Change Log:
>
>
> 1. Fixed the problem that "smartctl -a /dev/some_sata_disk -d ata"
> does not work on aic94xx device drive with SATA devices.
> The smartctl utility send down ATA smart command to aic94xx
> driver and fail to get the result which is stored on ATA output
> register.
> In normal case, Aic94xx’s firmware does not return the value of
> ATA output register to device driver due to performance reason.
> To solve this issue then the driver need to turn on internal
> flag (CSMI_TASK) for particular ATA command to enable firmware
> to return the value of ATA output register.
>
>
>
>
> Patch: apply to aic94xx-sas-2.6.git development tree
>
> Signed-off-by: Gilbert Wu <gilbert_wu@adaptec.com>
NAK
1) re-invents ATA command constants (a third time!).
Fix: use the constants in include/linux/ata.h
2) ignores the large number of ATA commands that also need register output.
Fix: invert the test. the only time when we do NOT want the ATA
register output is upon successful completion of "hot path" READ/WRITE
commands. For ALL other cases, we need the D2H FIS and/or SDB FIS data
reflecting register state.
3) Patches are normally imported by automated tools, and your email body
is copied directly into the permanent kernel changelog, archived for all
eternity. As such, you should format your patch description in a
similar fashion to other patches.
Fixes:
a) Subject line way too long and redundant. Use:
[PATCH] aic94xx: fix smartctl utility problem
Execute 'git log' in the kernel repository for more examples. The email
subject is always copied into the kernel changelog as the FIRST LINE of
the change. This is a one-line summary of your patch.
b) Do not write "Subject: [...]" in email body. Make this the subject
of your email, per guidelines at http://linux.yyz.us/patch-format.html
and Documentation/SubmittingPatches
c) Remove the redundant line
Contribution:
Gilbert Wu <gilbert_wu@adaptec.com>
(this is redundant to your email address in the email, and the
Signed-off-by line)
d) Remove the redundant line
Change Log:
(we already know its a changelog)
e) Move temporal and meta-comments after the "---" separator, so that
this text is not copied into the permanent kernel changelog. See
Documentation/SubmittingPatches for more info.
Regards,
Jeff
-
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 prev parent reply other threads:[~2007-08-31 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 18:03 [PATCH] scsi: Update Aic94xx SAS/SATA Linux open source device Gilbert Wu
2007-08-31 18:27 ` Jeff Garzik [this message]
2007-08-31 21:20 ` Gilbert Wu
2007-08-31 21:31 ` Douglas Gilbert
2007-08-31 23:56 ` Gilbert Wu
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=46D85DA4.1070008@garzik.org \
--to=jeff@garzik.org \
--cc=Gilbert_Wu@adaptec.com \
--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.