From: Jeff Garzik <jgarzik@pobox.com>
To: Brett Russ <russb@emc.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH libata-dev-2.6 05/05] libata: rework how CCs generated
Date: Wed, 23 Mar 2005 00:12:25 -0500 [thread overview]
Message-ID: <4240FAB9.5040200@pobox.com> (raw)
In-Reply-To: <20050317221753.0D09D0D9@lns1032.lss.emc.com>
Brett Russ wrote:
> 05_libata_split_ata_to_sense_error.patch
>
> This patch fixes several bugs as well as reorganizes the way
> check conditions are generated. Bugs fixed: 1) in
> ata_scsi_qc_complete(), ATA_12/16 commands wouldn't call
> ata_pass_thru_cc() on error status; 2) ata_pass_thru_cc()
> wouldn't put the SK, ASC, and ASCQ from ata_to_sense_error()
> in the correct place in the sense block because
> ata_to_sense_error() was writing a fixed sense block.
>
> Per the recommendations in the comments, ata_to_sense_error()
> is now split into 3 parts. The existing fcn is only used for
> outputting a sense key/ASC/ASCQ triplicate. A new function
> ata_dump_status() was created to print the error info, similar
> to the ide variety. A third function ata_gen_fixed_sense()
> was created to generate a fixed length sense block. I added
> the use of the info field for 28b LBAs only.
> ata_pass_thru_cc() renamed to ata_gen_ata_desc_sense() to
> match naming convention, presumably to include another
> descriptor format function in the future (see question 2
> below).
>
> Questions:
>
> 1) I made the ata_gen_..._sense() routines read the status
> register themselves rather than use the drv_stat values
> that used to be passed in? These values seemed
> unreliable/useless since they were often hard coded (see
> calls to ata_qc_complete() for origins of most drv_stat
> variables). Sound ok?
>
> 2) the SAT spec has little about error handling and sense
> information, sepcifically what descriptor format is valid
> for use by SAT commands. I want to use descriptor type 00
> (information) in my next patch until a spec says
> differently. Sound ok?
>
> Signed-off-by: Brett Russ <russb@emc.com>
Patch in general is OK, but I would prefer that it be split up a bit
more. Suggested split:
* whitespace changes (obscures reviewing the code)
* create and use ata_dump_status()
* the rest of the changes
Regards,
Jeff
next prev parent reply other threads:[~2005-03-23 5:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 22:20 [PATCH libata-dev-2.6 00/05] libata: scsi error handling improvements Brett Russ
2005-03-17 22:20 ` [PATCH libata-dev-2.6 01/05] libata: AHCI tf_read() support Brett Russ
2005-03-17 22:20 ` [PATCH libata-dev-2.6 02/05] libata: AHCI error handling fix Brett Russ
2005-03-17 22:20 ` [PATCH libata-dev-2.6 03/05] libata: update ATA PT sense desc code Brett Russ
2005-03-23 5:10 ` Jeff Garzik
2005-03-17 22:20 ` [PATCH libata-dev-2.6 04/05] libata: support descriptor sense in ctrl page Brett Russ
2005-03-23 4:24 ` Jeff Garzik
2005-03-17 22:20 ` [PATCH libata-dev-2.6 05/05] libata: rework how CCs generated Brett Russ
2005-03-23 5:12 ` Jeff Garzik [this message]
2005-03-23 20:36 ` [PATCH libata-dev-2.6 00/03] libata: scsi error handling improvements Brett Russ
2005-03-23 20:39 ` [PATCH libata-dev-2.6 01/03] libata: whitespace updates Brett Russ
2005-03-25 4:28 ` Jeff Garzik
2005-03-23 20:42 ` [PATCH libata-dev-2.6 02/03] libata: create/use ata_dump_status() Brett Russ
2005-03-23 20:45 ` [PATCH libata-dev-2.6 03/03] libata: rework check condition handling Brett Russ
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=4240FAB9.5040200@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=russb@emc.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 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.