[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAMRc=Mf+yuM-g1XMVpTvOXfMvf6t+saMJYfKXuCZU8fSfzxdtA@mail.gmail.com>
Date: Tue, 11 Feb 2025 16:38:01 +0100
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Wentao Liang <vulab@...as.ac.cn>
Cc: linus.walleij@...aro.org, mcoquelin.stm32@...il.com,
alexandre.torgue@...s.st.com, linux-gpio@...r.kernel.org,
linux-stm32@...md-mailman.stormreply.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] gpio: stmpe: Check return value of stmpe_reg_read in stmpe_gpio_irq_sync_unlock
On Tue, Feb 11, 2025 at 3:43 PM Wentao Liang <vulab@...as.ac.cn> wrote:
>
> The stmpe_reg_read function can fail, but its return value is not checked
> in stmpe_gpio_irq_sync_unlock. This can lead to silent failures and
> incorrect behavior if the hardware access fails.
>
> This patch adds checks for the return value of stmpe_reg_read. If the
> function fails, an error message is logged and the function returns
> early to avoid further issues.
>
Would you mind adding Fixes: and Cc: stable tags?
Bart
Powered by blists - more mailing lists