From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753504AbcDIH2A (ORCPT ); Sat, 9 Apr 2016 03:28:00 -0400 Received: from mbob.nabble.com ([162.253.133.15]:59960 "EHLO mbob.nabble.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751774AbcDIH17 (ORCPT ); Sat, 9 Apr 2016 03:27:59 -0400 X-Greylist: delayed 460 seconds by postgrey-1.27 at vger.kernel.org; Sat, 09 Apr 2016 03:27:59 EDT Date: Fri, 8 Apr 2016 23:20:22 -0700 (MST) From: pesa1 To: linux-kernel@vger.kernel.org Message-ID: <1460182822835-1347757.post@n7.nabble.com> Subject: .queuecommand field in struct scsi_host_template, for sas MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org While the following method, in drivers/scsi/libsas/sas_scsi_host:180 int sas_queuecommand(struct Scsi_Host *host, struct scsi_cmnd *cmd) seems to be the implementation for the `queuecommand` field of struct scsi_host_template. Where is it initialized so, for a general sas device? I can not find, in the code initialization for a scsi device, to the 'sas_queuecommand'. This is, while the scsi layer, clearly uses that field, in scsi_dispatch_command(): rtn = host->hostt->queuecommand(host, cmd); So, where does it get initialized?. Thanks -- View this message in context: http://linux-kernel.2935.n7.nabble.com/queuecommand-field-in-struct-scsi-host-template-for-sas-tp1347757.html Sent from the Linux Kernel mailing list archive at Nabble.com.