public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH] [RFC] Input: remove evbug driver
Date: Tue, 17 Dec 2024 13:57:27 -0800	[thread overview]
Message-ID: <Z2HzxziYyF9-vxns@google.com> (raw)
In-Reply-To: <8n377s5p-3r9n-ro38-3r2o-p536745552qo@xreary.bet>

On Tue, Dec 17, 2024 at 11:47:39AM +0100, Jiri Kosina wrote:
> From: Jiri Kosina <jkosina@suse.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@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'. 

Thanks.

-- 
Dmitry

  reply	other threads:[~2024-12-17 21:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-17 10:47 [PATCH] [RFC] Input: remove evbug driver Jiri Kosina
2024-12-17 21:57 ` Dmitry Torokhov [this message]
2024-12-19 17:57   ` Jiri Kosina
2024-12-19 18:01     ` Dmitry Torokhov

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=Z2HzxziYyF9-vxns@google.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@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