From: Jeff Garzik <jgarzik@pobox.com>
To: Albert Lee <albertcc@tw.ibm.com>
Cc: IDE Linux <linux-ide@vger.kernel.org>
Subject: Re: [PATCH libata-dev-2.6] ata_scsi_verify_xlat() fix
Date: Thu, 24 Feb 2005 02:44:02 -0500 [thread overview]
Message-ID: <421D85C2.6050103@pobox.com> (raw)
In-Reply-To: <421D7E5A.80702@tw.ibm.com>
Albert Lee wrote:
> --- libata-dev-2.6/drivers/scsi/libata-scsi.c 2005-02-21
> 17:23:03.000000000 +0800
> +++ libata-dev-2.6-mod/drivers/scsi/libata-scsi.c 2005-02-22
> 18:32:19.000000000 +0800
> @@ -785,6 +785,7 @@
> if ((cyl >> 16) || (head >> 4) || (sect >> 8) || (!sect))
> return 1;
>
> + tf->command = ATA_CMD_VERIFY;
> tf->nsect = n_block & 0xff; /* Sector count 0 means 256 sectors */
> tf->lbal = sect;
> tf->lbam = cyl;
> @@ -875,7 +876,7 @@
>
> /* Check and compose ATA command */
> if (!n_block)
> - /* In ATA, sector count 0 are 256 or 65536 sectors, not 0
> sectors. */
> + /* In ATA, sector count 0 means 256 or 65536 sectors, not 0
> sectors. */
> return 1;
>
Patch looks OK, but does not appear to be diff'd against
linux-2.6.11-rc4 + CHS support patches
When I try to apply your patch, I get
drivers/scsi/libata-scsi.c 1.68: 1661 lines
drivers/scsi/libata-scsi.c 1.68 -> 1.69: 1661 lines
2 out of 2 hunks FAILED -- saving rejects to file
drivers/scsi/libata-scsi.c.rej
When I examine your patch, I see that the line numbers are _way_ off:
my code line #622:
/* In ATA, sector count 0 are 256 or 65536 sectors, not 0 sector
your patch attempts to modify line #875 !!
> @@ -875,7 +876,7 @@
>
> /* Check and compose ATA command */
> if (!n_block)
> - /* In ATA, sector count 0 are 256 or 65536 sectors, not 0 sector
> s. */
> + /* In ATA, sector count 0 means 256 or 65536 sectors, not 0 sect
next prev parent reply other threads:[~2005-02-24 7:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 7:12 [PATCH libata-dev-2.6] ata_scsi_verify_xlat() fix Albert Lee
2005-02-24 7:44 ` Jeff Garzik [this message]
2005-02-25 4:58 ` Albert Lee
2005-02-25 5:28 ` Jeff Garzik
2005-02-25 7:52 ` Albert Lee
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=421D85C2.6050103@pobox.com \
--to=jgarzik@pobox.com \
--cc=albertcc@tw.ibm.com \
--cc=linux-ide@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).