linux-kernel - Re: [PATCH 2/2] input/navpoint: remove driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Tue, 16 Jan 2024 20:45:43 +0100
From: Duje Mihanović <duje.mihanovic@...le.hr>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: Russell King <linux@...linux.org.uk>,
 Uwe Kleine-König <u.kleine-koenig@...gutronix.de>,
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
 linux-input@...r.kernel.org
Subject: Re: [PATCH 2/2] input/navpoint: remove driver

Hello Dmitry,

On Tuesday, January 16, 2024 8:03:15 PM CET Dmitry Torokhov wrote:
> On Tue, Jan 16, 2024 at 07:17:48PM +0100, Duje Mihanović wrote:
> > This driver does not use the SPI core as it should, instead tampering
> > with the SSP registers manually. Besides this, it relies on the global
> > GPIO namespace. Refactoring the driver is almost certainly not worth it
> > as it was seemingly only implemented in the HP iPAQ hx4700 removed more
> > than a year ago in d6df7df7ae5a ("ARM: pxa: remove unused board files"),
> > so let's remove it.
> 
> I think this clashed with some recent cleanups to the navpoint driver.
> Could you please re-generate the patch against linux-next or my "next"
> branch please?

I have done it. Should I wait a bit (how much?) before resending or is it okay 
to send v2 right away in this case?

Regards,
--
Duje