From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Pali Rohár" <pali@kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
Thomas Maier <balagi@justmail.de>,
linux-block@vger.kernel.org
Subject: Re: [PATCH] pktcdvd: remove driver.
Date: Sat, 24 Dec 2022 13:24:39 +0100 [thread overview]
Message-ID: <Y6bvh48kTTzbMX6M@kroah.com> (raw)
In-Reply-To: <20221224101139.sgvhr2n3pbrs4agm@pali>
On Sat, Dec 24, 2022 at 11:11:39AM +0100, Pali Rohár wrote:
> On Saturday 24 December 2022 11:03:27 Greg Kroah-Hartman wrote:
> > On Sat, Dec 24, 2022 at 10:53:53AM +0100, Pali Rohár wrote:
> > > On Friday 02 December 2022 19:27:58 Greg Kroah-Hartman wrote:
> > > > Way back in 2016 in commit 5a8b187c61e9 ("pktcdvd: mark as unmaintained
> > > > and deprecated") this driver was marked as "will be removed soon". 5
> > > > years seems long enough to have it stick around after that, so finally
> > > > remove the thing now.
> > >
> > > Why to remove? This driver is still widely used, userspace in active
> > > maintenance and in last two years userspace software received more fixes
> > > for CD-RW support and pktcdvd.
> >
> > It was marked as "please remove" back in 2016, why wasn't that changed
> > if people were actually using this?
>
> And how should I know it if I was informed about it just today?
Using the "Why was I not informed?" defense isn't usually the best way
to discuss things when we have 800+ maintainers and 4000+ developers
here :)
> > > Just now community person informed me that somebody is going to remove
> > > kernel support.
> >
> > Isn't there better ways to support the hardware needed than this driver?
>
> Is there any other driver in kernel which provide block layer for it?
> I do not know about any other.
What about the venerable sg.c driver (enabled with CONFIG_CHR_DEV_SG)?
Does that not work properly for your specific hardware?
Anyway, have a nice holiday!
greg k-h
next prev parent reply other threads:[~2022-12-24 12:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 18:27 [PATCH] pktcdvd: remove driver Greg Kroah-Hartman
2022-12-02 19:35 ` Jens Axboe
2022-12-03 14:08 ` Greg Kroah-Hartman
2022-12-24 9:53 ` Pali Rohár
2022-12-24 10:03 ` Greg Kroah-Hartman
2022-12-24 10:11 ` Pali Rohár
2022-12-24 12:24 ` Greg Kroah-Hartman [this message]
2022-12-24 13:34 ` Pali Rohár
2022-12-24 15:14 ` Borislav Petkov
2022-12-24 15:48 ` Pali Rohár
2022-12-24 15:58 ` Borislav Petkov
2022-12-24 16:00 ` Pali Rohár
2022-12-24 16:18 ` Borislav Petkov
2022-12-24 16:36 ` Pali Rohár
2022-12-24 21:17 ` Keith Busch
2022-12-24 21:36 ` Pali Rohár
2022-12-24 21:46 ` Slade Watkins
2022-12-24 16:24 ` Pavel Machek
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=Y6bvh48kTTzbMX6M@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=axboe@kernel.dk \
--cc=balagi@justmail.de \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pali@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