All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Christoph Hellwig <hch@infradead.org>, linux-scsi@vger.kernel.org
Cc: Doug Ledford <dledford@redhat.com>
Subject: Re: [PATCH 5/4] scsi: remove MSG_*_TAG defines
Date: Fri, 28 Nov 2014 10:58:58 +0100	[thread overview]
Message-ID: <54784762.8020304@acm.org> (raw)
In-Reply-To: <20141124150725.GA23165@infradead.org>

On 11/24/14 16:07, Christoph Hellwig wrote:
> index 6719a33..2c5ce48 100644
> --- a/drivers/scsi/advansys.c
> +++ b/drivers/scsi/advansys.c
> @@ -7921,9 +7921,9 @@ static int asc_build_req(struct asc_board *boardp, struct scsi_cmnd *scp,
>   	 */
>   	if ((asc_dvc->cur_dvc_qng[scp->device->id] > 0) &&
>   	    (boardp->reqcnt[scp->device->id] % 255) == 0) {
> -		asc_scsi_q->q2.tag_code = MSG_ORDERED_TAG;
> +		asc_scsi_q->q2.tag_code = ORDERED_QUEUE_TAG;
>   	} else {
> -		asc_scsi_q->q2.tag_code = MSG_SIMPLE_TAG;
> +		asc_scsi_q->q2.tag_code = SIMPLE_QUEUE_TAG;
>   	}
>
>   	/* Build ASC_SCSI_Q */
> @@ -8351,7 +8351,7 @@ static int AscPutReadyQueue(ASC_DVC_VAR *asc_dvc, ASC_SCSI_Q *scsiq, uchar q_no)
>   	}
>   	q_addr = ASC_QNO_TO_QADDR(q_no);
>   	if ((scsiq->q1.target_id & asc_dvc->use_tagged_qng) == 0) {
> -		scsiq->q2.tag_code &= ~MSG_SIMPLE_TAG;
> +		scsiq->q2.tag_code &= ~SIMPLE_QUEUE_TAG;
>   	}
>   	scsiq->q1.status = QS_FREE;
>   	AscMemWordCopyPtrToLram(iop_base,
> @@ -8669,7 +8669,7 @@ static int AscExeScsiQueue(ASC_DVC_VAR *asc_dvc, ASC_SCSI_Q *scsiq)
>   		}
>   	}
>   	if (disable_syn_offset_one_fix) {
> -		scsiq->q2.tag_code &= ~MSG_SIMPLE_TAG;
> +		scsiq->q2.tag_code &= ~SIMPLE_QUEUE_TAG;
>   		scsiq->q2.tag_code |= (ASC_TAG_FLAG_DISABLE_ASYN_USE_SYN_FIX |
>   				       ASC_TAG_FLAG_DISABLE_DISCONNECT);
>   	} else {

One of the statements in advansys.c (tag_code &= 0xDC) makes assumptions 
about the numeric value of MSG_SIMPLE_TAG. This makes me wonder whether 
it is safe to change MSG_SIMPLE_TAG into another value ?

Bart.

  reply	other threads:[~2014-11-28 10:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24 14:36 queue_type fixups Christoph Hellwig
2014-11-24 14:36 ` [PATCH 1/4] scsi: remove ->change_queue_type method Christoph Hellwig
2014-11-28  9:59   ` Bart Van Assche
2014-12-03 13:32   ` Hannes Reinecke
2014-12-04  9:10     ` Christoph Hellwig
2014-12-04  2:27   ` Martin K. Petersen
2014-11-24 14:36 ` [PATCH 2/4] scsi: never drop to untagged mode during queue ramp down Christoph Hellwig
2014-11-28  9:59   ` Bart Van Assche
2014-12-03 13:32   ` Hannes Reinecke
2014-12-04  2:28   ` Martin K. Petersen
2014-11-24 14:36 ` [PATCH 3/4] scsi: remove scsi_get_tag_type Christoph Hellwig
2014-11-28 10:00   ` Bart Van Assche
2014-12-03 13:33   ` Hannes Reinecke
2014-12-04  2:28   ` Martin K. Petersen
2014-11-24 14:36 ` [PATCH 4/4] scsi: remove scsi_set_tag_type Christoph Hellwig
2014-11-28 10:00   ` Bart Van Assche
2014-12-03 13:34   ` Hannes Reinecke
2014-12-04  2:29   ` Martin K. Petersen
2014-11-24 15:07 ` [PATCH 5/4] scsi: remove MSG_*_TAG defines Christoph Hellwig
2014-11-28  9:58   ` Bart Van Assche [this message]
2014-12-01  9:03     ` Christoph Hellwig
2014-12-01 11:44       ` Bart Van Assche
2014-12-04  2:31   ` Martin K. Petersen
2014-12-03  9:32 ` queue_type fixups Christoph Hellwig

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=54784762.8020304@acm.org \
    --to=bvanassche@acm.org \
    --cc=dledford@redhat.com \
    --cc=hch@infradead.org \
    --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.