From: Pat LaVarre <p.lavarre@ieee.org>
To: Jens Axboe <axboe@suse.de>
Cc: linux-scsi@vger.kernel.org
Subject: cdrom sr ide-cd - CDC_WR, 1999 op x46 GPCMD_GET_CONFIGURATION
Date: 28 Nov 2003 13:05:03 -0700 [thread overview]
Message-ID: <1070049902.11739.3.camel@patrh9> (raw)
Jens A:
Am I correct to think we/you have no interest in going ahead and merging
into 2.6.1 a purely restructuring patch that supposedly changes no
results? That is,
1) I should Not construct a patch that does no more than add op x46
GPCMD_GET_CONFIGURATION.
2) Nor should I construct a patch that does no more than add a new
CDC_WR flag to control pass thru of writes without overloading
CDC_DVD_RAM.
Instead I should wait to write such code until After we actually do
dream up a good way to discover, without waiting for the disc to arrive,
that some PDT x05 DVD/CD devices besides DVD-RAM are randomly rewritable
in place.
Right? That's what I've been doing, without anyone's explicit
agreement, but then suddenly I thought perhaps I should ask Someone With
Change Authority, hi.
Pat LaVarre
next reply other threads:[~2003-11-28 20:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-28 20:05 Pat LaVarre [this message]
2003-11-29 21:49 ` cdrom sr ide-cd - CDC_WR, 1999 op x46 GPCMD_GET_CONFIGURATION Pat LaVarre
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=1070049902.11739.3.camel@patrh9 \
--to=p.lavarre@ieee.org \
--cc=axboe@suse.de \
--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