From: James Bottomley <James.Bottomley@steeleye.com>
To: "Smart, James" <James.Smart@Emulex.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
"'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: RE: [Announce] Emulex LightPulse Device Driver
Date: 10 Mar 2004 20:10:54 -0500 [thread overview]
Message-ID: <1078967456.10834.80.camel@mulgrave> (raw)
In-Reply-To: <3356669BBE90C448AD4645C843E2BF2802C014F1@xbl.ma.emulex.com>
On Wed, 2004-03-10 at 17:47, Smart, James wrote:
> we receive comments. There are constructs in the driver that are likely not
> going to change, such as the logging facility. How contentious is this ?
> What about the IP interfaces? and so on. Anything we receive, especially on
> the larger concepts in the driver, only helps us understand what's ahead.
Well, what your logging facility tries to do (discriminated messages to
the console based on a mask) is extremely standard for drivers. The way
you implement it is slightly, erm, less than desirable. Having your own
version of sprintf in your driver is a definite no-no (why do you do
this? You never seem actually to use the added formatting characters
like %E?). But at least it doesn't do anything silly like try to ouput
to the serial port.
As far as the IP portion goes: layering and separation should really be
the order of the day---perhaps even to the point where you have a core
module with a scsi and an IP one that sit on top of it.
> Our plans are to complete most of the work list on the FAQ by early April.
> We'll try to make weekly drops on SourceForge, with each snapshot containing
> a log of the changes. Once the code base matures, we will ping the lists
> again, asking for feedback.
OK, I'll look forward to it.
James
next prev parent reply other threads:[~2004-03-11 1:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-10 22:47 [Announce] Emulex LightPulse Device Driver Smart, James
2004-03-11 1:10 ` James Bottomley [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-09 22:45 Smart, James
2004-03-10 0:09 ` Stefan Smietanowski
2004-03-10 7:21 ` vda
2004-03-10 8:35 ` Jeff Garzik
2004-03-10 15:21 ` James Bottomley
[not found] ` <mailman.1078908361.15239.linux-kernel2news@redhat.com>
2004-03-10 17:59 ` Pete Zaitcev
2004-03-10 17:59 ` Pete Zaitcev
2004-03-10 18:04 ` 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=1078967456.10834.80.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=James.Smart@Emulex.com \
--cc=jgarzik@pobox.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 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.