From: Bart Van Assche <bart.vanassche@sandisk.com>
To: Yann Droneaud <ydroneaud@opteya.com>
Cc: James Bottomley <jbottomley@parallels.com>,
Hannes Reinecke <hare@suse.de>,
Sagi Grimberg <sagig@mellanox.com>,
Sebastian Parschauer <sebastian.riemer@profitbricks.com>,
Brian King <brking@linux.vnet.ibm.com>,
Nathan Fontenot <nfont@linux.vnet.ibm.com>,
Tyrel Datwyler <tyreld@linux.vnet.ibm.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
linux-rdma <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH, resend] IB/srp: Add 64-bit LUN support
Date: Wed, 4 Mar 2015 16:54:08 +0100 [thread overview]
Message-ID: <54F72AA0.1070903@sandisk.com> (raw)
In-Reply-To: <1425474982.3069.21.camel@opteya.com>
On 03/04/15 14:16, Yann Droneaud wrote:
> Le mercredi 04 mars 2015 à 11:01 +0100, Bart Van Assche a écrit :
>> diff --git a/drivers/infiniband/ulp/srp/ib_srp.c b/drivers/infiniband/ulp/srp/ib_srp.c
>> index a0e24a8..e427454 100644
>> --- a/drivers/infiniband/ulp/srp/ib_srp.c
>> +++ b/drivers/infiniband/ulp/srp/ib_srp.c
>> @@ -3146,7 +3146,7 @@ static ssize_t srp_create_target(struct device *dev,
>> target_host->transportt = ib_srp_transport_template;
>> target_host->max_channel = 0;
>> target_host->max_id = 1;
>> - target_host->max_lun = SRP_MAX_LUN;
>> + target_host->max_lun = -1LL;
>
> I guess you can remove SRP_MAX_LUN from
> drivers/infiniband/ulp/srp/ib_srp.h too.
Hello Yann,
That sounds like a good idea to me. I will update this patch accordingly.
Bart.
--
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
prev parent reply other threads:[~2015-03-04 15:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 10:01 [PATCH, resend] IB/srp: Add 64-bit LUN support Bart Van Assche
2015-03-04 11:41 ` Sagi Grimberg
[not found] ` <54F6D7ED.3080606-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2015-03-04 13:16 ` Yann Droneaud
2015-03-04 15:54 ` Bart Van Assche [this message]
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=54F72AA0.1070903@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=brking@linux.vnet.ibm.com \
--cc=hare@suse.de \
--cc=jbottomley@parallels.com \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nfont@linux.vnet.ibm.com \
--cc=sagig@mellanox.com \
--cc=sebastian.riemer@profitbricks.com \
--cc=tyreld@linux.vnet.ibm.com \
--cc=ydroneaud@opteya.com \
/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).