linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	Vojtech Pavlik <vojtech@ucw.cz>, Jiri Kosina <jikos@kernel.org>,
	Benjamin Tissoires <bentiss@kernel.org>
Subject: Re: [RFC PATCH 0/5] Removal of a few obsolete input drivers
Date: Mon, 12 Aug 2024 09:46:54 -0700	[thread overview]
Message-ID: <Zro8fpgvqa74aki4@google.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2408121448250.59022@angie.orcam.me.uk>

On Mon, Aug 12, 2024 at 02:53:30PM +0100, Maciej W. Rozycki wrote:
> On Sun, 11 Aug 2024, Dmitry Torokhov wrote:
> 
> > > > I am wondering if it is not the time to retire bus mice drivers since
> > > > they have been out of favor for close to 30 years, as well as 3 drivers
> > > > for portables from late '90s to early 2000.
> > > 
> > >  Are these drivers broken, e.g. fail to compile or crash the system?  
> > 
> > I have no idea because I doubt that anyone has tested them since
> > forever.
> 
>  What's the rationale for your conclusion?  How do you know nobody uses 
> them?

Because they are either require ISA add-on cards and it is quite hard to
find devices that still work, and are supported by the current kernel,
or internal peripherals in devices that are no longer useful. Do you
expect anyone using "Gateway AOL Connected Touchpad" in the year of our
Lord 2024?

> 
> > > Otherwise what's the gain from removal?
> > 
> > The same gain that we get from removing obsolete boards and
> > architectures - less maintenance burden, less work when we need to
> > change some APIs, less energy burnt by 0-day and other bots, CI systems,
> > etc, compiling useless drivers over and over and over.
> 
>  Well, you don't have do do anything about these drivers, do you?  They 
> don't scream for food.  And as to the energy, well I doubt this really 
> matters, the amount is noise lost in the overall consumption.

I kind of do even if they did not require much involvement.

Let me ask this: why do you want to keep them? Do you know of a large
(or small) userbase of bus mice enthusiasts? Note that it would be very
easy to "git revert" the removal if someone actually needs this.

Thanks.

-- 
Dmitry

  reply	other threads:[~2024-08-12 16:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-08 17:27 [RFC PATCH 0/5] Removal of a few obsolete input drivers Dmitry Torokhov
2024-08-08 17:27 ` [RFC PATCH 1/5] Input: inport - remove driver Dmitry Torokhov
2024-08-08 17:27 ` [RFC PATCH 2/5] Input: logibm " Dmitry Torokhov
2024-08-08 17:27 ` [RFC PATCH 3/5] Input: pc110pad " Dmitry Torokhov
2024-08-08 17:27 ` [RFC PATCH 4/5] Input: mk712 " Dmitry Torokhov
2024-08-08 17:27 ` [RFC PATCH 5/5] Input: ct82c710 " Dmitry Torokhov
2024-08-09  0:24 ` [RFC PATCH 0/5] Removal of a few obsolete input drivers Maciej W. Rozycki
2024-08-12  4:50   ` Dmitry Torokhov
2024-08-12 13:53     ` Maciej W. Rozycki
2024-08-12 16:46       ` Dmitry Torokhov [this message]
2024-08-15 21:20         ` Maciej W. Rozycki
2024-10-22 20:55           ` Dmitry Torokhov

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=Zro8fpgvqa74aki4@google.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=bentiss@kernel.org \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@orcam.me.uk \
    --cc=vojtech@ucw.cz \
    /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;
as well as URLs for NNTP newsgroup(s).