[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <176648930565.697163.2533356435881488772.b4-ty@kernel.org>
Date: Tue, 23 Dec 2025 16:58:25 +0530
From: Vinod Koul <vkoul@...nel.org>
To: Maxime Coquelin <mcoquelin.stm32@...il.com>,
Alexandre Torgue <alexandre.torgue@...s.st.com>,
Clément Le Goffic <legoffic.clement@...il.com>,
Amelie Delaunay <amelie.delaunay@...s.st.com>
Cc: dmaengine@...r.kernel.org, linux-stm32@...md-mailman.stormreply.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Clément Le Goffic <clement.legoffic@...s.st.com>
Subject: Re: [PATCH v2] dmaengine: stm32-mdma: initialize m2m_hw_period and
ccr to fix warnings
On Wed, 17 Dec 2025 09:15:03 +0100, Amelie Delaunay wrote:
> m2m_hw_period is initialized only when chan_config->m2m_hw is true. This
> triggers a warning:
> ‘m2m_hw_period’ may be used uninitialized [-Wmaybe-uninitialized]
> Although m2m_hw_period is only used when chan_config->m2m_hw is true and
> ignored otherwise, initialize it unconditionally to 0.
>
> ccr is initialized by stm32_mdma_set_xfer_param() when the sg list is not
> empty. This triggers a warning:
> ‘ccr’ may be used uninitialized [-Wmaybe-uninitialized]
> Indeed, it could be used uninitialized if the sg list is empty. Initialize
> it to 0.
>
> [...]
Applied, thanks!
[1/1] dmaengine: stm32-mdma: initialize m2m_hw_period and ccr to fix warnings
commit: aaf3bc0265744adbc2d364964ef409cf118d193d
Best regards,
--
~Vinod
Powered by blists - more mailing lists