From: Jens Axboe <axboe@suse.de>
To: "O.Sezer" <sezeroz@ttnet.net.tr>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
linux-kernel@vger.kernel.org
Subject: Re: status of cdrom patches for 2.4 ?
Date: Wed, 24 Nov 2004 16:05:20 +0100 [thread overview]
Message-ID: <20041124150520.GG13847@suse.de> (raw)
In-Reply-To: <41A49DA5.9090900@ttnet.net.tr>
On Wed, Nov 24 2004, O.Sezer wrote:
> Jens Axboe wrote:
> >On Wed, Nov 24 2004, Marcelo Tosatti wrote:
> >
> >>On Wed, Nov 24, 2004 at 01:11:13AM +0200, O.Sezer wrote:
> >>
> >>>Hi all:
> >>>
> >>>What are the status of the cdrom patches for 2.4 series?
> >>>Namely the dvd patches which are dropped while in the
> >>>27-rc era, and the cd-mrw patch which never had a chance
> >>>trying to go in to 2.4. Jens? Mancelo?
> >>
> >>There were problems with the DVD-RW patches so I reverted them.
>
> Yup. Pat then posted a patch which supposedly fixed it by placing
> something like
> else if (CDROM_CAN(CDC_DVD_RAM))
> ret = 0;
> in cdrom_open_write():
> http://marc.theaimsgroup.com/?t=109156838400001&r=1&w=2
> http://marc.theaimsgroup.com/?l=linux-scsi&m=109156820507518&w=2
>
> Jens' MRW patch also introduces a new function: cdrom_dvdram_open_write
> (which, in turn, calls cdrom_media_erasable), CDROM_CAN(CDC_DVD_RAM)
> check in cdrom_open_write() is assigned to it; which again is supposed
> to fix it.
Fix that issue. More might crop up.
> >>Jens, what do you think?
> >
> >
> >I don't think it's worth the bother, the support is in 2.6. And I don't
> >want to maintain new atapi stuff for 2.4. Pat used to care about the
> >patches, but as he is no longer with Iomega I don't think there's anyone
> >to look after it.
>
> Which is truly a pity. Yes I can understand that a maintainer needs
> to concentrate on new trees etc, but it's pity. Especially hearing
> the pre-recorded "Hey 2.6 already has it, upgrade to it" message is
> always nice ;)
You conveniently ignore that 2.4 is in bug fix mode, and a strict one
now even. And then you want to add new features to a driver that is both
used on almost every machine and also drives the most picky and buggy
hardware out there? So please can the 'pre-recorded' message crap. You
are not the one that will have to pick up the pieces if something
breaks.
--
Jens Axboe
next prev parent reply other threads:[~2004-11-24 15:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 23:11 status of cdrom patches for 2.4 ? O.Sezer
2004-11-24 7:43 ` Marcelo Tosatti
2004-11-24 12:53 ` Jens Axboe
2004-11-24 14:41 ` O.Sezer
2004-11-24 15:05 ` Jens Axboe [this message]
2004-11-24 15:07 ` O.Sezer
2004-11-24 15:17 ` Jens Axboe
2004-11-24 15:21 ` O.Sezer
2004-11-24 15:23 ` Jens Axboe
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=20041124150520.GG13847@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=sezeroz@ttnet.net.tr \
/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.