[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ss361op7-9op7-pr29-5pr7-4867rqn1rqo4@xreary.bet>
Date: Thu, 19 Dec 2024 18:57:48 +0100 (CET)
From: Jiri Kosina <jikos@...nel.org>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
cc: linux-kernel@...r.kernel.org, linux-input@...r.kernel.org
Subject: Re: [PATCH] [RFC] Input: remove evbug driver
On Tue, 17 Dec 2024, Dmitry Torokhov 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.
Thanks Dmitry.
I don't see it in dtor/input.git though .. ?
> 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'.
The dmesg on those architectures must be a real pleasure to read :)
> Thanks.
Thanks,
--
Jiri Kosina
SUSE Labs
Powered by blists - more mailing lists