From: Dave Boutcher <sleddog@us.ibm.com>
To: linux-scsi@vger.kernel.org
Subject: new scsi driver etiquette
Date: Fri, 09 Jan 2004 11:44:44 -0600 [thread overview]
Message-ID: <usmipxbhv.fsf@us.ibm.com> (raw)
After the recent discussions on people bypassing the linux-scsi list
with their scsi code, I would not dream of such a faux pas. I'm about
to submit a bunch of code for your collective review.
If I have a couple of big new driver files (e.g. 3500+ lines), what is
the most appropriate format for review? Just include them inline
in a mailing to the list? I'm not quite ready to send them as a
formal patch.
Thanks,
Dave B
next reply other threads:[~2004-01-09 17:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 17:44 Dave Boutcher [this message]
2004-01-09 17:56 ` new scsi driver etiquette Christoph Hellwig
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=usmipxbhv.fsf@us.ibm.com \
--to=sleddog@us.ibm.com \
--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.