From: Jeff Garzik <jeff@garzik.org>
To: James.Smart@Emulex.Com
Cc: "Darrick J. Wong" <djwong@us.ibm.com>,
Andrew Vasquez <andrew.vasquez@qlogic.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Alexis Bruemmer <alexisb@us.ibm.com>,
James Bottomley <james.bottomley@steeleye.com>
Subject: Re: [PATCH] aic94xx: Use request_firmware() to provide SAS address if the adapter lacks one
Date: Wed, 10 Oct 2007 11:40:10 -0400 [thread overview]
Message-ID: <470CF25A.9050403@garzik.org> (raw)
In-Reply-To: <470CE78B.2080509@emulex.com>
James Smart wrote:
> So, what's the decision - are we only allowing this for physical adapters
> that don't have a name ? or are we allowing it to be more dynamic ?
At a minimum, I think(?) we all agree that current upstream aic94xx
behavior is nice: allow the admin to override the WWN manually, even if
the adapter already has one.
As to the question of request_firmware() versus sysfs, it's IMO largely
a question of taste -- do you like the "get property" on-demand pull
model, or a push model that presumes the property must be set before it
is needed? And which solution requires the least amount of additional
userspace machinery in order to be usable?
Jeff
next prev parent reply other threads:[~2007-10-10 15:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 21:25 [PATCH] aic94xx: Use request_firmware() to provide SAS address if the adapter lacks one Darrick J. Wong
2007-10-08 22:48 ` Andrew Vasquez
2007-10-08 23:50 ` Darrick J. Wong
2007-10-09 0:12 ` Andrew Vasquez
2007-10-09 15:29 ` James Smart
2007-10-09 16:41 ` Andrew Vasquez
2007-10-09 17:06 ` Darrick J. Wong
2007-10-10 14:54 ` James Smart
2007-10-10 15:40 ` Jeff Garzik [this message]
2007-10-10 19:38 ` Luben Tuikov
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=470CF25A.9050403@garzik.org \
--to=jeff@garzik.org \
--cc=James.Smart@Emulex.Com \
--cc=alexisb@us.ibm.com \
--cc=andrew.vasquez@qlogic.com \
--cc=djwong@us.ibm.com \
--cc=james.bottomley@steeleye.com \
--cc=linux-kernel@vger.kernel.org \
--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