From: "Pali Rohár" <pali@kernel.org>
To: Borislav Petkov <bp@alien8.de>
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 16:48:42 +0100 [thread overview]
Message-ID: <20221224154842.o4ngrwmskduowttm@pali> (raw)
In-Reply-To: <Y6cXRbGUsarzoJEw@zn.tnic>
On Saturday 24 December 2022 16:14:13 Borislav Petkov wrote:
> On Sat, Dec 24, 2022 at 02:34:25PM +0100, Pali Rohár wrote:
> > And asking question back is not the best way too.
>
> Maybe I'm missing something here but is there a logic/rule somewhere
> which says to inform *you* when this driver gets removed?!
Do you think that it is fully illogical to never inform and ignore
userspace projects which are under active maintenance and are using
kernel APIs and kernel drivers which somebody decided to remove?
> I can't find one, ./scripts/get_maintainer.pl doesn't say so either.
>
> --
> Regards/Gruss,
> Boris.
>
> https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-12-24 15:48 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 [this message]
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=20221224154842.o4ngrwmskduowttm@pali \
--to=pali@kernel.org \
--cc=axboe@kernel.dk \
--cc=balagi@justmail.de \
--cc=bp@alien8.de \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.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