From: "Josef Möllers" <josef.moellers@fujitsu-siemens.com>
To: Kurt Garloff <garloff@suse.de>
Cc: Patrick Mansfield <patmans@us.ibm.com>,
linux-scsi@vger.kernel.org, "Wichert,
Gerhard" <Gerhard.Wichert@fujitsu-siemens.com>
Subject: Re: Why REPORT LUN only for SCSI-2?
Date: Fri, 18 Jul 2003 08:38:13 +0200 [thread overview]
Message-ID: <3F1795D5.F1FBECFB@fujitsu-siemens.com> (raw)
In-Reply-To: 20030717184909.GD2520@nbkurt.garloff.de
Kurt Garloff wrote:
> > As a side note (probably starting a new thread) why does BLIST_LARGELUN
> > override max_scsi_luns?
>
> It shouldn't. Did I really do this? (... checking 2.4 code ...)
> No, I plead innocent.
Oops, I didn't check the info I got from a third party or I should go
and wash my ears B-{(
It's SPARSELUN which overrides max_scsi_luns:
if (bflags & BLIST_SPARSELUN) {
*max_dev_lun = shpnt->max_lun;
*sparse_lun = 1;
return 1;
}
The objection still stands ...
--
Josef Möllers (Pinguinpfleger bei FSC)
If failure had no penalty success would not be a prize
-- T. Pratchett
-
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:[~2003-07-18 6:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 14:18 Why REPORT LUN only for SCSI-2? Josef Möllers
2003-07-15 14:39 ` Patrick Mansfield
2003-07-16 7:00 ` Josef Möllers
2003-07-16 19:35 ` Patrick Mansfield
2003-07-17 8:55 ` Josef Möllers
2003-07-17 18:49 ` Kurt Garloff
2003-07-17 23:46 ` Patrick Mansfield
2003-07-18 6:38 ` Josef Möllers [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-18 0:25 David.Egolf
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=3F1795D5.F1FBECFB@fujitsu-siemens.com \
--to=josef.moellers@fujitsu-siemens.com \
--cc=Gerhard.Wichert@fujitsu-siemens.com \
--cc=garloff@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=patmans@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.