On Tue, 17 Dec 2024, Dmitry Torokhov wrote: > > From: Jiri Kosina <jkosina@xxxxxxxx> > > > > 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. Thanks Dmitry. I don't see it in dtor/input.git though .. ? > Interestingly: > > dtor@dtor-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'. The dmesg on those architectures must be a real pleasure to read :) > Thanks. Thanks, -- Jiri Kosina SUSE Labs
