From: Jens Axboe <axboe@suse.de>
To: Pat LaVarre <p.lavarre@ieee.org>
Cc: linux-scsi@vger.kernel.org, John McKell <McKellj@iomega.com>
Subject: Re: CDC_RAM for lk 2.4, PATCH proposed
Date: Fri, 21 May 2004 08:53:15 +0200 [thread overview]
Message-ID: <20040521065312.GK1952@suse.de> (raw)
In-Reply-To: <1085090500.3822.20.camel@patibmrh9>
On Thu, May 20 2004, Pat LaVarre wrote:
> diff confirms for me the patch inline of this post matches what John
> McKell posted, except for the trivial difference of folder names & dates
> and the substantive difference that I did comment out the per-open
> printk:
>
> - + printk("cdrom: %s opening for WRITE\n", current->comm);
> + + /* printk("cdrom: %s opening for WRITE\n", current->comm); */
That's fine, I killed that in 2.6 as well.
> > > I believe 2.4.18 patch actually makes `mount -w` work there by way of
> > > "see all DVD/CD drives as DVD-RAM/ DVD-ROM compatible".
> >
> > But that's not what the patch does at all. The patch simply says "If we
> > succeeded in retriving the mode capability page, ignore what it says and
> > flag the drive as dvd-rom/ram capable" which is clearly bogus.
>
> To newbie me, this is not clearly bogus, sorry.
>
> 1)
>
> I see my 2.4.18 patch makes `mount -w` work, by way of breaking `cat
> /proc/sys/dev/cdrom/info`.
>
> mount matters more to me than proc.
>
> Besides, the breakage is small. I'm not falsely claiming that a DVD-RAM
> disc is present. I'm only falsely claiming that a DVD-RAM disc could be
> present. Software that branches visibly on which kind of disc might
> someday be present looks very nearly bogus to me.
Sorry, I still think this is completely bogus. No point in debating it,
there's no way that hack will go into the 2.4 kernels.
> 2)
>
> I see my 2.4.18 patch is extremely short and simple.
>
> Simplicity in the patch matters more to me the further I step back from
> the latest available at kernel.org.
Your 2.4.18 patch is a hack.
> diff -Nurp linux-2.4.27-pre3/include/linux/cdrom.h linux-2.4.27-pre3-pel/include/linux/cdrom.h
[snip]
Patch looks fine to me, I'll send it to Marcelo for inclusion. Thanks!
--
Jens Axboe
next prev parent reply other threads:[~2004-05-21 6:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-15 16:52 CDC_RAM for lk 2.4, PATCH proposed Pat LaVarre
2004-04-16 12:09 ` Jens Axboe
2004-04-23 22:25 ` John McKell
2004-04-28 1:46 ` Pat LaVarre
2004-04-28 14:48 ` Pat LaVarre
[not found] ` <1084897080.3746.38.camel@patibmrh9>
2004-05-19 8:15 ` Jens Axboe
2004-05-19 15:45 ` Pat LaVarre
2004-05-20 8:06 ` Jens Axboe
2004-05-20 22:01 ` Pat LaVarre
2004-05-20 23:51 ` Pat LaVarre
2004-05-21 6:53 ` Jens Axboe [this message]
2004-05-21 15:28 ` Pat LaVarre
2004-06-03 18:30 ` Pat LaVarre
2004-06-03 18:32 ` Jens Axboe
2004-06-04 14:53 ` Marcelo Tosatti
2004-06-04 15:18 ` Pat LaVarre
2004-06-04 15:24 ` Jens Axboe
2004-06-04 15:27 ` Pat LaVarre
2004-06-04 15:36 ` Jens Axboe
2004-06-18 21:42 ` 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=20040521065312.GK1952@suse.de \
--to=axboe@suse.de \
--cc=McKellj@iomega.com \
--cc=linux-scsi@vger.kernel.org \
--cc=p.lavarre@ieee.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.