From: Javier Martinez Canillas <javierm@redhat.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Linux Input <linux-input@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: Removal of cyttsp4 driver from mainline Linux kernel
Date: Sun, 04 Aug 2024 15:36:41 +0200 [thread overview]
Message-ID: <87frrk8l5i.fsf@minerva.mail-host-address-is-not-set> (raw)
In-Reply-To: <2024080301-unlikable-sepia-49cb@gregkh>
Greg Kroah-Hartman <gregkh@linuxfoundation.org> writes:
Hello Dmitry,
> On Fri, Aug 02, 2024 at 11:10:14PM -0700, Dmitry Torokhov wrote:
>> On Fri, Aug 02, 2024 at 11:08:51PM -0700, Dmitry Torokhov wrote:
>> > Hi,
>> >
>> > cyttsp4 touchscreen driver was contributed by Cypress in 2013 and since
>> > then has seen no updates. The driver uses platform data (no device tree
>> > support) and there are no users of it in the mainline kernel. There were
>> > occasional fixes to it for issues either found by static ocde analysis
>> > tools or visual inspection, but otherwise the driver is completely
>> > untested.
>> >
>> > Should it be removed?
>> >
>> > Thanks.
>>
>> And of course vendor email is bouncing...
>
I contributed that driver because was working at the time on upstreaming
support for the OMAP3 Nook Color eReader from Barnes & Noble, but never
made that much progress on it. And even though I still have that tablet,
it has been in a box for more than a decade so unlikely I'll ever do it.
> Sound like a good reason to drop it. If anyone needs it back it can be
> reverted and fixed up easily then.
>
Agreed.
--
Best regards,
Javier Martinez Canillas
Core Platforms
Red Hat
prev parent reply other threads:[~2024-08-04 13:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-03 6:08 Removal of cyttsp4 driver from mainline Linux kernel Dmitry Torokhov
2024-08-03 6:10 ` Dmitry Torokhov
2024-08-03 6:33 ` Greg Kroah-Hartman
2024-08-04 13:36 ` Javier Martinez Canillas [this message]
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=87frrk8l5i.fsf@minerva.mail-host-address-is-not-set \
--to=javierm@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-input@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;
as well as URLs for NNTP newsgroup(s).