linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: linux-ide@vger.kernel.org, Alexander Sabourenkov <screwdriver@lxnt.info>
Subject: Re: [PATCH 2.6.24-rc1] sata_promise: ASIC PRD table bug workaround
Date: Mon, 29 Oct 2007 15:07:06 -0400	[thread overview]
Message-ID: <47262F5A.8070804@garzik.org> (raw)
In-Reply-To: <200710291550.l9TFocYf018050@harpo.it.uu.se>

Mikael Pettersson wrote:
> @@ -155,7 +155,7 @@ static struct scsi_host_template pdc_ata
>  	.queuecommand		= ata_scsi_queuecmd,
>  	.can_queue		= ATA_DEF_QUEUE,
>  	.this_id		= ATA_SHT_THIS_ID,
> -	.sg_tablesize		= LIBATA_MAX_PRD,
> +	.sg_tablesize		= LIBATA_MAX_PRD-1,
>  	.cmd_per_lun		= ATA_SHT_CMD_PER_LUN,
>  	.emulated		= ATA_SHT_EMULATED,
>  	.use_clustering		= ATA_SHT_USE_CLUSTERING,

IMO, this will be difficult for human eyes to see, many months from now.

I would prefer a 'PDC_MAX_PRD' constant, defined to this value.


> @@ -530,7 +608,7 @@ static void pdc_qc_prep(struct ata_queue
>  
>  	switch (qc->tf.protocol) {
>  	case ATA_PROT_DMA:
> -		ata_qc_prep(qc);
> +		pdc_fill_sg(qc);
>  		/* fall through */
>  
>  	case ATA_PROT_NODATA:
> @@ -546,11 +624,11 @@ static void pdc_qc_prep(struct ata_queue
>  		break;
>  
>  	case ATA_PROT_ATAPI:
> -		ata_qc_prep(qc);
> +		pdc_fill_sg(qc);
>  		break;
>  
>  	case ATA_PROT_ATAPI_DMA:
> -		ata_qc_prep(qc);
> +		pdc_fill_sg(qc);
>  		/*FALLTHROUGH*/

Note that this is not exactly an equivalent change -- you are removing 
the test in ata_qc_prep() that occurs prior to ata_fill_sg() call.

	Jeff



  reply	other threads:[~2007-10-29 19:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-29 15:50 [PATCH 2.6.24-rc1] sata_promise: ASIC PRD table bug workaround Mikael Pettersson
2007-10-29 19:07 ` Jeff Garzik [this message]
2007-10-30  6:09   ` Alexander Sabourenkov
  -- strict thread matches above, loose matches on Subject: below --
2007-10-30  9:07 Mikael Pettersson
2007-10-30  9:22 ` Alexander Sabourenkov

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=47262F5A.8070804@garzik.org \
    --to=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    --cc=screwdriver@lxnt.info \
    /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).