From: Pat LaVarre <p.lavarre@ieee.org>
To: Jens Axboe <axboe@suse.de>
Cc: linux-scsi@vger.kernel.org,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
John McKell <McKellj@iomega.com>
Subject: Re: [PATCH] DVD-RAM rewritable again
Date: 04 Aug 2004 05:35:47 -0600 [thread overview]
Message-ID: <1091619347.5681.6.camel@patibmrh9> (raw)
In-Reply-To: <20040804045839.GA8139@suse.de>
> > @@ -536,6 +536,8 @@ static int cdrom_open_write(struct cdrom
> > if (CDROM_CAN(CDC_RAM) &&
> > !CDROM_CAN(CDC_CD_R|CDC_CD_RW|CDC_DVD|CDC_DVD_R))
> > ret = cdrom_ram_open_write(cdi);
> > + else if (CDROM_CAN(CDC_DVD_RAM))
> > + ret = 0;
> ...
> That looks fine!
Good to hear, I was not certain.
Can I/ should I do anything more to help, ... before we begin the 2.4.28
work of making USB DVD-RAM discs also rewritable, same as USB Iomega REV
discs?
Pat LaVarre
P.S. I notice kernel.org changing in parallel with this thread:
--- http://www.kernel.org/pub/linux/kernel/v2.4/testing/patch-2.4.27.log
...
Summary of changes from v2.4.27-rc4 to v2.4.27-rc5
...
Marcelo Tosatti:
o Revert DVD-RW write support for now: axboe@suse.de|ChangeSet|20040606235035|46544
o Cset exclude: axboe@suse.de|ChangeSet|20040607195639|57919
...
---
Me the kernelnewbie, I don't yet know how to click thru to a ChangeSet
to see specifically what these summaries mean.
next prev parent reply other threads:[~2004-08-04 11:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-03 21:21 [PATCH] DVD-RAM rewritable again Pat LaVarre
2004-08-04 4:58 ` Jens Axboe
2004-08-04 11:35 ` Pat LaVarre [this message]
2004-08-04 11:38 ` Jens Axboe
2004-08-17 15:19 ` dvd-ram open succeeds despite write-protect Pat LaVarre
2004-08-04 11:57 ` [PATCH] DVD-RAM rewritable again Marcelo Tosatti
2004-08-20 22:40 ` 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=1091619347.5681.6.camel@patibmrh9 \
--to=p.lavarre@ieee.org \
--cc=McKellj@iomega.com \
--cc=axboe@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.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