From: Patrice CHOTARD <patrice.chotard@foss.st.com>
To: Mark Brown <broonie@kernel.org>
Cc: <linux-spi@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <christophe.kerello@foss.st.com>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: spi: stm32-qspi: Fix stm32_qspi_transfer_one_message() error path
Date: Fri, 26 Aug 2022 11:21:39 +0200 [thread overview]
Message-ID: <5bd8dfad-de31-a5ac-2efc-a9a3d80650f0@foss.st.com> (raw)
In-Reply-To: <20220826091851.1393266-1-patrice.chotard@foss.st.com>
Hi Mark
Patch sent with incorrect commit title, a new one is in the pipe.
Sorry for that
Patrice
On 8/26/22 11:18, patrice.chotard@foss.st.com wrote:
> From: Patrice Chotard <patrice.chotard@foss.st.com>
>
> The patch a557fca630cc: "spi: stm32_qspi: Add transfer_one_message()
> spi callback" from Aug 23, 2022, leads to the following Smatch static
> checker warning:
>
> drivers/spi/spi-stm32-qspi.c:627 stm32_qspi_transfer_one_message()
> error: uninitialized symbol 'ret'.Fix the following Smatch static checker warning:
>
> Fixes: a557fca630cc ("spi: stm32_qspi: Add transfer_one_message() spi callback")
> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
> Signed-off-by: Patrice Chotard <patrice.chotard@foss.st.com>
> ---
> drivers/spi/spi-stm32-qspi.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/spi/spi-stm32-qspi.c b/drivers/spi/spi-stm32-qspi.c
> index 92459daca95f..679fd1c34f7e 100644
> --- a/drivers/spi/spi-stm32-qspi.c
> +++ b/drivers/spi/spi-stm32-qspi.c
> @@ -562,7 +562,7 @@ static int stm32_qspi_transfer_one_message(struct spi_controller *ctrl,
> struct spi_transfer *transfer;
> struct spi_device *spi = msg->spi;
> struct spi_mem_op op;
> - int ret;
> + int ret = 0;
>
> if (!spi->cs_gpiod)
> return -EOPNOTSUPP;
> @@ -592,8 +592,10 @@ static int stm32_qspi_transfer_one_message(struct spi_controller *ctrl,
> dummy_bytes = transfer->len;
>
> /* if happens, means that message is not correctly built */
> - if (list_is_last(&transfer->transfer_list, &msg->transfers))
> + if (list_is_last(&transfer->transfer_list, &msg->transfers)) {
> + ret = -EINVAL;
> goto end_of_transfer;
> + }
>
> transfer = list_next_entry(transfer, transfer_list);
> }
prev parent reply other threads:[~2022-08-26 9:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 9:18 spi: stm32-qspi: Fix stm32_qspi_transfer_one_message() error path patrice.chotard
2022-08-26 9:21 ` Patrice CHOTARD [this message]
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=5bd8dfad-de31-a5ac-2efc-a9a3d80650f0@foss.st.com \
--to=patrice.chotard@foss.st.com \
--cc=broonie@kernel.org \
--cc=christophe.kerello@foss.st.com \
--cc=dan.carpenter@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
/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;
as well as URLs for NNTP newsgroup(s).