linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Christoph Hellwig <hch@lst.de>
Cc: James Bottomley <jbottomley@parallels.com>,
	Matthew Wilcox <matthew@wil.cx>,
	Doug Gilbert <dgilbert@interlog.com>,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH 02/12] advansys: use shared host tag map for command lookup
Date: Thu, 04 Dec 2014 10:25:41 +0100	[thread overview]
Message-ID: <54802895.5010900@suse.de> (raw)
In-Reply-To: <20141204092043.GD23891@lst.de>

On 12/04/2014 10:20 AM, Christoph Hellwig wrote:
>>  typedef struct asc_scsiq_2 {
>> -	ASC_VADDR srb_ptr;
>> +	__le32 srb_tag;
> 
> Given that the tag has no meaning for the hardware why do you
> want to endian switch it?  Keeping the ASC_VADDR for now makes
> it easier to verify the hardware structures don't change.
> 
Mhm. See the patch I've just sent to Ondrej.
For the narrow board it actually _has_ a meaning.
But okay, the endian switch is probably pointless here.

>> @@ -6132,6 +6077,13 @@ static void adv_async_callback(ADV_DVC_VAR *adv_dvc_varp, uchar code)
>>  		AdvResetChipAndSB(adv_dvc_varp);
>>  		break;
>>  
>> +	case ADV_ASYNC_CARRIER_READY_FAILURE:
>> +		/*
>> +		 * Carrier not ready; abort the command.
>> +		 */
>> +		ASC_DBG(0, "ADV_ASYNC_CARRIER_READY_FAILURE\n");
>> +		break;
>> +
> 
> Where does this one come from?
> 
Encountered during debugging, I just thought to have it printed.
But okay, I can move it into a separate patch.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 21284 (AG Nürnberg)
--
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

  reply	other threads:[~2014-12-04  9:25 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-03 11:44 [PATCH 00/12] nobody loves the advansys driver Hannes Reinecke
2014-12-03 11:44 ` [PATCH 01/12] advansys: use host_reset Hannes Reinecke
2014-12-04  9:17   ` Christoph Hellwig
2014-12-04  9:23     ` Hannes Reinecke
2014-12-03 11:44 ` [PATCH 02/12] advansys: use shared host tag map for command lookup Hannes Reinecke
2014-12-04  9:20   ` Christoph Hellwig
2014-12-04  9:25     ` Hannes Reinecke [this message]
2014-12-04  9:26       ` Christoph Hellwig
2014-12-03 11:44 ` [PATCH 03/12] advansys: use DMA-API for mapping sense buffer Hannes Reinecke
2014-12-03 11:44 ` [PATCH 04/12] advansys: Use DMA-API for carrier buffer Hannes Reinecke
2014-12-03 11:44 ` [PATCH 05/12] advansys: Use DMA-API for mapping request blocks Hannes Reinecke
2014-12-03 11:44 ` [PATCH 06/12] advansys: Use dma_pool for sg elements Hannes Reinecke
2014-12-03 11:45 ` [PATCH 07/12] advansys: use 'bool' instead of 'int' Hannes Reinecke
2014-12-03 11:45 ` [PATCH 08/12] advansys: use standard data types Hannes Reinecke
2014-12-03 11:45 ` [PATCH 09/12] advansys: Remove 'TRUE' and 'FALSE' definitions Hannes Reinecke
2014-12-03 11:45 ` [PATCH 10/12] advansys: Remove 'ERR' definition Hannes Reinecke
2014-12-03 11:45 ` [PATCH 11/12] advansys: cleanup function return codes Hannes Reinecke
2014-12-03 11:45 ` [PATCH 12/12] advansys: Update to version 3.5 and remove compilation warning Hannes Reinecke
2014-12-04  9:23   ` Christoph Hellwig
2014-12-04  9:26     ` Hannes Reinecke
2014-12-03 15:21 ` [PATCH 00/12] nobody loves the advansys driver Christoph Hellwig
2014-12-03 15:34   ` Ondrej Zary
2014-12-03 15:42     ` James Bottomley
2014-12-03 16:28       ` Hannes Reinecke
2014-12-04  9:13       ` hch
2014-12-04  9:12     ` Christoph Hellwig
2014-12-03 16:06 ` Douglas Gilbert
2014-12-03 18:29 ` Ondrej Zary
2014-12-04  7:12   ` Hannes Reinecke
2014-12-07 14:44     ` Ondrej Zary

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=54802895.5010900@suse.de \
    --to=hare@suse.de \
    --cc=dgilbert@interlog.com \
    --cc=hch@lst.de \
    --cc=jbottomley@parallels.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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).