From: sashiko-bot@kernel.org
To: "Breno Rodrigues Alves" <breno3011alves@gmail.com>
Cc: linux-clk@vger.kernel.org, dmitry.torokhov@gmail.com,
linux-pci@vger.kernel.org, linux-input@vger.kernel.org,
media-ci@linuxtv.org
Subject: Re: [PATCH v5] Kconfig: fix typos in core makefiles and purge defective DVB debug (v5)
Date: Sat, 05 Sep 2026 00:41:02 +0000 [thread overview]
Message-ID: <20260905004102.8FDEC1F00A3D@smtp.kernel.org> (raw)
In-Reply-To: <20260905003005.118245-1-breno3011alves@gmail.com>
> Automated review from Sashiko AI revealed that re-enabling the legacy
> DVB_ULE_DEBUG code via CONFIG_DVB_ULE_DEBUG exposes severe race conditions
> on global state variables, leading to out-of-bounds memory corruption.
> Additionally, the debug block suffers from undeclared identifiers (TS_SZ).
>
> Following the core kernel principle of eliminating dangerous, unmaintained
> code, this patch completely extirpates the defective DVB_ULE_DEBUG block
> from dvb_net.c and purges its corresponding configuration symbol from
> the Kconfig tree.
>
> This version retains the verified MediaTek bugfixes and ghost purges:
> - Fixes MediaTek interconnect typo mapping mt8196.o to MT8196.
> - Fixes MediaTek regulator typo mapping mt6316-regulator to MT6316.
> - Cleans up the dangling comment in drivers/leds/Kconfig.
> - Purges verified legacy ghost weight.
>
> Signed-off-by: Breno Rodrigues Alves <breno3011alves@gmail.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260905003005.118245-1-breno3011alves@gmail.com?part=1
next prev parent reply other threads:[~2026-09-05 0:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 0:30 [PATCH v5] Kconfig: fix typos in core makefiles and purge defective DVB debug (v5) Breno Rodrigues Alves
2026-09-05 0:41 ` sashiko-bot [this message]
2026-09-07 6:59 ` Thomas Zimmermann
2026-09-09 14:54 ` Dan Carpenter
2026-09-10 0:11 ` kernel test robot
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=20260905004102.8FDEC1F00A3D@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=breno3011alves@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=media-ci@linuxtv.org \
--cc=sashiko-reviews@lists.linux.dev \
/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