linux-kernel - Re: [PATCH] [RFC] Input: remove evbug 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] [day] [month] [year] [list]

Message-ID: <Z2HzxziYyF9-vxns@google.com>
Date: Tue, 17 Dec 2024 13:57:27 -0800
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Jiri Kosina <jikos@...nel.org>
Cc: linux-kernel@...r.kernel.org, linux-input@...r.kernel.org
Subject: Re: [PATCH] [RFC] Input: remove evbug driver

On Tue, Dec 17, 2024 at 11:47:39AM +0100, Jiri Kosina wrote:
> From: Jiri Kosina <jkosina@...e.com>
> 
> I've never heard of anyone having used this driver for debugging at least 
> in over past decade or so. Since we have tools like evtest, this driver 
> seems to be rather superficial.
> 
> Also, it apparently causes confusion among people who accidentaly enable 
> CONFIG_INPUT_EVBUG and are annoyed/confused by their kernel log being 
> spammed by a lot of useless data.
> 
> Let's just remove it.

Agree. Applied, thank you.

Interestingly:

dtor@...r-ws:~/kernel/next $ git grep -i evbug
arch/arm/configs/davinci_all_defconfig:CONFIG_INPUT_EVBUG=m
arch/arm/configs/imx_v6_v7_defconfig:CONFIG_INPUT_EVBUG=m
arch/arm/configs/moxart_defconfig:CONFIG_INPUT_EVBUG=y
arch/arm/configs/omap1_defconfig:CONFIG_INPUT_EVBUG=y
arch/mips/configs/pic32mzda_defconfig:CONFIG_INPUT_EVBUG=m
arch/sh/configs/sh7785lcr_32bit_defconfig:CONFIG_INPUT_EVBUG=m
arch/sparc/configs/sparc32_defconfig:CONFIG_INPUT_EVBUG=m

I am curious why moxart and omap1 have it as 'y'. 

Thanks.

-- 
Dmitry