From: Christoph Hellwig <hch@infradead.org>
To: Linux-SCSI Mailing List <linux-scsi@vger.kernel.org>,
James Bottomley <James.Bottomley@SteelEye.com>
Subject: Re: PATCH [2/5] qla2xxx: add remote port codes...
Date: Wed, 13 Apr 2005 22:40:23 +0100 [thread overview]
Message-ID: <20050413214023.GA18161@infradead.org> (raw)
In-Reply-To: <20050413191824.GK9703@plap.qlogic.org>
> +#include <linux/version.h>
not needed (this is in qla_attr.c)
> +struct scsi_transport_template *
> +qla2x00_alloc_transport_tmpl(void)
> +{
> + return (fc_attach_transport(&qla2xxx_transport_functions));
> +}
I don't see much of a point in this function vs just making
qla2xxx_transport_functions non-static.
> --- a/drivers/scsi/qla2xxx/qla_gbl.h 2005-04-13 08:38:23.000000000 -0700
> +++ b/drivers/scsi/qla2xxx/qla_gbl.h 2005-04-13 08:42:33.000000000 -0700
> @@ -24,6 +24,7 @@
> #define __QLA_GBL_H
>
> #include <linux/interrupt.h>
> +#include <scsi/scsi_transport.h>
shouldn't be needed, a simple forward-declaration of
struct scsi_transport_template should do it.
> atomic_set(&fcport->state, FCS_ONLINE);
> + if (ha->flags.init_done)
> + qla2x00_reg_remote_port(ha, fcport);
> }
...
> - goto probe_failed;
> + goto probe_alloc_failed;
> }
>
> + pci_set_drvdata(pdev, ha);
> + host->this_id = 255;
> + host->cmd_per_lun = 3;
> + host->unique_id = ha->instance;
> + host->max_cmd_len = MAX_CMDSZ;
> + host->max_channel = ha->ports - 1;
> + host->max_id = ha->max_targets;
> + host->max_lun = ha->max_luns;
> + host->transportt = qla2xxx_transport_template;
> + if (scsi_add_host(host, &pdev->dev))
> + goto probe_alloc_failed;
> +
> + qla2x00_alloc_sysfs_attr(ha);
> +
> if (qla2x00_initialize_adapter(ha) &&
> !(ha->device_flags & DFLG_NO_CABLE)) {
Now this I don't undersant. You're moving the host registration earlier,
maybe too earlier but I haven't checked that yet, why do you still need
the special case for delaying registration of the targets?
Also please propagate the full error that scsi_add_host returned.
next prev parent reply other threads:[~2005-04-13 21:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-13 19:15 PATCH [0/5] qla2xxx: remote port rework Andrew Vasquez
2005-04-13 19:18 ` PATCH [1/5] qla2xxx: remove internal queuing Andrew Vasquez
2005-04-13 19:18 ` PATCH [2/5] qla2xxx: add remote port codes Andrew Vasquez
2005-04-13 21:40 ` Christoph Hellwig [this message]
2005-04-19 6:33 ` Andrew Vasquez
2005-04-19 7:27 ` Andrew Vasquez
2005-04-19 21:13 ` Christoph Hellwig
2005-05-20 6:17 ` Jeremy Higdon
2005-05-20 15:15 ` Andrew Vasquez
2005-05-27 7:51 ` Jeremy Higdon
2005-04-17 15:18 ` James Bottomley
2005-04-13 19:18 ` PATCH [3/5] qla2xxx: remove lun discovery codes Andrew Vasquez
2005-04-13 19:19 ` PATCH [4/5] qla2xxx: cleanup DMA mappings Andrew Vasquez
2005-04-13 21:34 ` Christoph Hellwig
2005-04-15 18:06 ` Andrew Vasquez
2005-04-13 19:19 ` PATCH [5/5] qla2xxx: remove /proc interface Andrew Vasquez
2005-04-13 19:42 ` PATCH [0/5] qla2xxx: remote port rework Matthew Wilcox
2005-04-13 20:50 ` PATCH [6/5] qla2xxx: update version :) Andrew Vasquez
2005-04-13 20:57 ` James Bottomley
2005-04-13 21:24 ` Andrew Vasquez
2005-04-19 21:15 ` Christoph Hellwig
2005-04-22 7:22 ` Andrew Vasquez
2005-04-24 10:53 ` Christoph Hellwig
2005-04-13 21:17 ` Christoph Hellwig
2005-04-15 17:38 ` Andrew Vasquez
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=20050413214023.GA18161@infradead.org \
--to=hch@infradead.org \
--cc=James.Bottomley@SteelEye.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox