public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: "Pali Rohár" <pali@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	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 17:18:51 +0100	[thread overview]
Message-ID: <Y6cma26FKzBQD8AN@zn.tnic> (raw)
In-Reply-To: <20221224160055.ln3dbhx7dnut7dwi@pali>

On Sat, Dec 24, 2022 at 05:00:55PM +0100, Pali Rohár wrote:
> Maybe it would be a wise to read a documentation which is in the kernel
> source tree?

I guess you mean udftools...

> Or at least read the deletion patch itself as it is linked from there?

You mean the documentation file is pointed at there?

> Or what else could be easier than this?

Well, apparently it ain't as easy because people do not necessarily see
it how you see it. That's why I'm asking.

I have removed ancient stuff in the past myself and it is not always
easy to go dig out who uses it and whether it is used at all in the
first place.

And people do not always reply and projects are dead and they maybe use
it but the machine which has this hw hasn't been booted for a decade and
it ain't worth the enegry to power it back on and so so on and so on...

So you don't have to get all worked up about it - if it is really used,
I'm sure the maintainers involved will do the right decision. The point
is, finding out whether something still has users and with the latest
kernel is not always trivial.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

  reply	other threads:[~2022-12-24 16:19 UTC|newest]

Thread overview: 17+ 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
     [not found] ` <20221224095353.w32xhmyzlft6qi4v@pali>
2022-12-24 10:03   ` Greg Kroah-Hartman
2022-12-24 10:11     ` Pali Rohár
2022-12-24 12:24       ` Greg Kroah-Hartman
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 [this message]
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=Y6cma26FKzBQD8AN@zn.tnic \
    --to=bp@alien8.de \
    --cc=axboe@kernel.dk \
    --cc=balagi@justmail.de \
    --cc=gregkh@linuxfoundation.org \
    --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