From: Luben Tuikov <ltuikov@yahoo.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Michael Reed <mdr@sgi.com>,
James.Smart@Emulex.Com, linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: generating a Linux WWN?
Date: Tue, 2 Oct 2007 22:31:51 -0700 (PDT) [thread overview]
Message-ID: <50432.44268.qm@web31802.mail.mud.yahoo.com> (raw)
In-Reply-To: <470327C9.9060103@garzik.org>
--- Jeff Garzik <jeff@garzik.org> wrote:
> Luben Tuikov wrote:
> > --- Jeff Garzik <jeff@garzik.org> wrote:
> >> Luben Tuikov wrote:
> >>> --- Jeff Garzik <jeff@garzik.org> wrote:
> >>>> Luben Tuikov wrote:
> >>>>> This still does not justify "let's generate it in the kernel".
> >>>> Once an admin specifies to use an alternate WWN provision, the method
> >>>> used to obtain that WWN is an implementation detail and irrelevant.
> >>> But you're arguing that the kernel should generate it to "help out"
> >>> SAS drivers with HW that has had it's MS/NVRAM erased or corrupted.
> >>>
> >>> The kernel has no business generating SAS WWN.
> >> Perhaps you missed the English text "once an admin specifies" in the
> >> quoted email.
> >
> > Was your "once an admin specifies" reply to my email
> > supposed to be "Oh, I see, generating a SAS WWN in the kernel
> > is not that good an idea after all. I'll implement it
> > as a kernel/module option." ?
>
> The admin will have the option to auto-generate a WWN, should they so
> desire.
What does that mean? "auto-generate"? By whom?
What if they don't "auto-generate" (whatever that means)?
next prev parent reply other threads:[~2007-10-03 5:31 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 10:04 generating a Linux WWN? Jeff Garzik
2007-09-27 13:55 ` Michael Reed
2007-09-27 14:04 ` James Smart
2007-09-27 14:16 ` Patrick_Boyd
2007-09-27 14:46 ` Matthew Wilcox
2007-09-27 15:07 ` Michael Reed
2007-09-27 15:12 ` Michael Reed
2007-09-27 23:40 ` Jeff Garzik
2007-09-27 22:48 ` Jeff Garzik
2007-10-01 10:56 ` Andi Kleen
2007-09-27 14:19 ` Jeff Garzik
2007-09-27 14:29 ` Michael Reed
2007-09-27 15:30 ` Douglas Gilbert
2007-09-27 22:32 ` Jeff Garzik
2007-09-27 23:12 ` Jeff Garzik
2007-10-02 23:47 ` Luben Tuikov
2007-10-03 0:35 ` Jeff Garzik
2007-10-03 3:45 ` Luben Tuikov
2007-10-03 4:15 ` Jeff Garzik
2007-10-03 5:12 ` Luben Tuikov
2007-10-03 5:25 ` Jeff Garzik
2007-10-03 5:31 ` Luben Tuikov [this message]
2007-10-03 5:45 ` Jeff Garzik
2007-10-03 14:59 ` Douglas Gilbert
2007-10-03 16:16 ` Jeff Garzik
2007-10-03 18:02 ` Matthew Jacob
2007-10-03 18:09 ` Jeff Garzik
2007-10-03 19:44 ` Luben Tuikov
2007-10-03 20:25 ` Jeff Garzik
2007-10-03 22:08 ` Luben Tuikov
2007-10-03 22:17 ` David Miller
2007-10-04 0:11 ` Luben Tuikov
2007-10-04 3:23 ` Matthew Jacob
2007-10-04 3:27 ` Jeff Garzik
2007-10-04 3:33 ` Matthew Wilcox
2007-10-05 22:09 ` James Bottomley
2007-10-05 22:11 ` David Miller
2007-10-05 22:14 ` James Bottomley
2007-10-05 22:17 ` David Miller
2007-10-05 22:41 ` Jeff Garzik
2007-10-05 22:49 ` David Miller
2007-10-05 22:52 ` Jeff Garzik
2007-10-06 14:11 ` James Bottomley
2007-10-06 14:36 ` Jeff Garzik
2007-10-06 15:04 ` James Bottomley
2007-10-06 15:23 ` Jeff Garzik
2007-10-06 15:33 ` James Bottomley
2007-10-06 15:42 ` Jeff Garzik
2007-10-08 18:42 ` Luben Tuikov
2007-10-07 2:48 ` David Miller
2007-10-08 15:41 ` Michael Reed
2007-10-08 18:34 ` Luben Tuikov
2007-10-07 2:46 ` David Miller
2007-10-08 18:18 ` Luben Tuikov
2007-10-03 5:38 ` Luben Tuikov
2007-10-03 5:47 ` Jeff Garzik
2007-10-03 15:33 ` Michael Reed
2007-10-03 16:02 ` Jeff Garzik
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=50432.44268.qm@web31802.mail.mud.yahoo.com \
--to=ltuikov@yahoo.com \
--cc=James.Smart@Emulex.Com \
--cc=jeff@garzik.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mdr@sgi.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