From: David Jander <david@protonic.nl>
To: Mark Brown <broonie@kernel.org>
Cc: linux-spi@vger.kernel.org, Andy Shevchenko <andy.shevchenko@gmail.com>
Subject: Re: [PATCH 3/3] spi: spi.c: Remove redundant else block
Date: Wed, 29 Jun 2022 16:28:57 +0200 [thread overview]
Message-ID: <20220629162857.7cadc15e@erd992> (raw)
In-Reply-To: <20220629142519.3985486-4-david@protonic.nl>
On Wed, 29 Jun 2022 16:25:19 +0200
David Jander <david@protonic.nl> wrote:
> Reported-by: Andy Shevchenko <andy.shevchenko@gmail.com>
> Signed-off-by: David Jander <david@protonic.nl>
> ---
> drivers/spi/spi.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/spi/spi.c b/drivers/spi/spi.c
> index 09d4959bc09c..dc1a324e3271 100644
> --- a/drivers/spi/spi.c
> +++ b/drivers/spi/spi.c
> @@ -1636,13 +1636,13 @@ static int __spi_pump_transfer_message(struct spi_controller *ctlr,
> dev_err(&ctlr->dev,
> "failed to transfer one message from queue\n");
> return ret;
> - } else {
> - WRITE_ONCE(ctlr->cur_msg_need_completion, true);
> - smp_mb(); /* see spi_finalize_current_message()... */
> - if (READ_ONCE(ctlr->cur_msg_incomplete))
> - wait_for_completion(&ctlr->cur_msg_completion);
> }
>
> + WRITE_ONCE(ctlr->cur_msg_need_completion, true);
> + smp_mb(); /* See spi_finalize_current_message()... */
Argh. Just noticed that this comment fix slipped into the wrong patch.
Do I need to re-submit, or is this acceptable?
> + if (READ_ONCE(ctlr->cur_msg_incomplete))
> + wait_for_completion(&ctlr->cur_msg_completion);
> +
> return 0;
> }
>
Best regards,
--
David Jander
next prev parent reply other threads:[~2022-06-29 14:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 14:25 [PATCH 0/3] Fix some coding style issues David Jander
2022-06-29 14:25 ` [PATCH 1/3] spi: spi.c: White-space fix in __spi_pump_messages() David Jander
2022-06-29 14:25 ` [PATCH 2/3] spi: spi.c: Fix comment style David Jander
2022-06-29 14:25 ` [PATCH 3/3] spi: spi.c: Remove redundant else block David Jander
2022-06-29 14:28 ` David Jander [this message]
2022-06-29 14:34 ` Mark Brown
2022-06-30 14:17 ` [PATCH 0/3] Fix some coding style issues Mark Brown
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=20220629162857.7cadc15e@erd992 \
--to=david@protonic.nl \
--cc=andy.shevchenko@gmail.com \
--cc=broonie@kernel.org \
--cc=linux-spi@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;
as well as URLs for NNTP newsgroup(s).