On Tue, 2015-04-07 at 17:45 +0200, Christoph Hellwig wrote: > On Tue, Apr 07, 2015 at 10:49:07AM +0200, Hannes Reinecke wrote: > > 'tproto' specifies the transport protocol, not the device type. > > So use the correct definitions here. > > > > Signed-off-by: Hannes Reinecke <hare@xxxxxxx> > > This looks correct, but opens up questions: I'm not entirely convinced it is. I think the correct value might be SAS_PROTOCOL_SATA | SAS_PROTOCOL_STP which is the same numeric value as SAS_SATA_DEV. STP is the SATA Tunnelling Protocol. It's what you use to talk to an expander with a directly attached SATA device on one of its ports. SAS_PROTOCOL_SATA means talk directly to the device using SATA (not SAS tunnelled SATA) and is only appropriate for a SATA device directly attached to the SAS initiator. This function is examining an expander phy, so the initiator will always have to speak STP to it, regardless of what the actual value is. James > - how did you find this? > - why didn't we notice earlier? > > Also I wonder if we should move to more __bitwise types for these > kinds of things.. > -- > To unsubscribe from this list: send the line "unsubscribe linux-scsi" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
