From: Hannes Reinecke <hare@suse.de>
To: Tejun Heo <tj@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
James Bottomley <jbottomley@parallels.com>,
linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCH 1/4] libata: consolidate ata_dev_classify()
Date: Sat, 06 Sep 2014 10:21:51 +0200 [thread overview]
Message-ID: <540AC41F.8020506@suse.de> (raw)
In-Reply-To: <20140905234241.GH15723@mtj.dyndns.org>
On 09/06/2014 01:42 AM, Tejun Heo wrote:
> Hello, Hannes.
>
> Sorry about the delay.
>
> On Wed, Jul 30, 2014 at 09:55:08AM +0200, Hannes Reinecke wrote:
>> ata_dev_classify() just uses the 'lbah' and 'lbam'
>> fields from the taskfile, so we can as well use those
>> as arguments and rip out the custom code from sas_ata.
>
> I wonder whether it'd easier to just make sas code pass in
> ata_taskfile instead? The interface which takes three consecutive
> u8's is kinda error-prone.
>
Well, yes, in principle. I was looking into that, too.
But then I figured that moving to ata_taskfile would be a major overhaul
for libsas, which would be quite beyond scope here.
And all for a puny little patch.
>> --- a/drivers/scsi/aic94xx/aic94xx_task.c
>> +++ b/drivers/scsi/aic94xx/aic94xx_task.c
>> @@ -373,10 +373,10 @@ static int asd_build_ata_ascb(struct asd_ascb *ascb, struct sas_task *task,
>>
>> if (unlikely(task->ata_task.device_control_reg_update))
>> scb->header.opcode = CONTROL_ATA_DEV;
>> - else if (dev->sata_dev.command_set == ATA_COMMAND_SET)
>> - scb->header.opcode = INITIATE_ATA_TASK;
>> - else
>> + else if (dev->sata_dev.class == ATA_DEV_ATAPI)
>> scb->header.opcode = INITIATE_ATAPI_TASK;
>> + else
>> + scb->header.opcode = INITIATE_ATA_TASK;
>
> Are these changes covered by the patch description? Looks like the
> patch is mixing two separate logical changes.
>
Okay, I'll be splitting them up.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (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
next prev parent reply other threads:[~2014-09-06 8:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 7:55 [PATCHv4 0/4] Initial SMR drive support Hannes Reinecke
2014-07-30 7:55 ` [PATCH 1/4] libata: consolidate ata_dev_classify() Hannes Reinecke
2014-09-05 23:42 ` Tejun Heo
2014-09-06 8:21 ` Hannes Reinecke [this message]
2014-09-06 12:52 ` Tejun Heo
2014-09-07 11:24 ` Hannes Reinecke
2014-09-07 16:02 ` Tejun Heo
2014-07-30 7:55 ` [PATCH 2/4] libata: Implement ATA_DEV_ZAC Hannes Reinecke
2014-07-30 7:55 ` [PATCH 3/4] libata-scsi: Update SATL for ZAC drives Hannes Reinecke
2014-09-05 23:44 ` Tejun Heo
2014-07-30 7:55 ` [PATCH 4/4] sd: Optionally attach to ZBC devices Hannes Reinecke
-- strict thread matches above, loose matches on Subject: below --
2014-07-29 14:45 [PATCHv3 0/4] Initial SMR drive support Hannes Reinecke
2014-07-29 14:45 ` [PATCH 1/4] libata: consolidate ata_dev_classify() Hannes Reinecke
2014-07-21 8:27 [PATCHv2 0/4] Initial SMR drive support Hannes Reinecke
2014-07-21 8:27 ` [PATCH 1/4] libata: consolidate ata_dev_classify() Hannes Reinecke
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=540AC41F.8020506@suse.de \
--to=hare@suse.de \
--cc=dan.j.williams@intel.com \
--cc=hch@infradead.org \
--cc=jbottomley@parallels.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=tj@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).