From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Larry.Finger@lwfinger.net, florian.c.schilhabel@googlemail.com,
gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org,
Sathish Kumar <skumark1902@gmail.com>
Cc: Sathish Kumar <skumark1902@gmail.com>
Subject: Re: [PATCH v3] staging: rtl8712: Use completions for signaling
Date: Thu, 24 Mar 2022 10:02:17 +0100 [thread overview]
Message-ID: <3422492.iIbC2pHGDl@leap> (raw)
In-Reply-To: <20220323045515.2513-1-skumark1902@gmail.com>
On mercoledì 23 marzo 2022 05:55:15 CET Sathish Kumar wrote:
> r8712_sitesurvey_cmd() uses a variable to notify r8712_SetFilter() that it
> has completed operation. There is no sort of assurance that the variable will
> actually change and it could cache the value the first time it is read and
> then never update it for the whole loop logic.
>
> Use completion variables because they are better suited for the purpose.
>
> This patch fixes the checkpatch.pl warnings like:
> CHECK: Avoid CamelCase: <blnEnableRxFF0Filter>
> + u8 blnEnableRxFF0Filter;
>
> Signed-off-by: Sathish Kumar <skumark1902@gmail.com>
> ---
> Changes in v2:
> - Remove the "bln" prefix
>
> Changes in v3:
> - Replace the variable used for signaling with completion
> ---
> drivers/staging/rtl8712/drv_types.h | 3 +--
> drivers/staging/rtl8712/rtl871x_cmd.c | 2 +-
> drivers/staging/rtl8712/usb_intf.c | 2 +-
> drivers/staging/rtl8712/xmit_linux.c | 8 +-------
> 4 files changed, 4 insertions(+), 11 deletions(-)
>
Hi Sathish,
First of all, I must admit that you have impressed me :)
Aside from the specific code of this driver that I don't know and aside
from the specific problem that you've been suggested to fix, I see that
you have been able to research and understand the subjects that Greg and
I talked to you about.
By reading what Greg wrote soon after me, I believe that he was expecting
a slight different solution. I suggest you to read carefully what he writes
rather than what I write, just because he has at least 20 or more years
of experience than me and because I'm just a spare time type of kernel
developer.
You chose to use wait_for_completion() / complete() (notice that these API
use barriers indirectly). What I can say is that they look to be suited for
solving the issues that you have here, even if there are other approaches.
Since, as said, it looks like you have understood how to select and use the
one of the API that were suggested, you have my...
Reviewed-by: Fabio M. De Francesco <fmdefrancesco@gmail.com>
Thanks,
Fabio
prev parent reply other threads:[~2022-03-24 9:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 4:55 [PATCH v3] staging: rtl8712: Use completions for signaling Sathish Kumar
2022-03-24 9:02 ` Fabio M. De Francesco [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=3422492.iIbC2pHGDl@leap \
--to=fmdefrancesco@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=florian.c.schilhabel@googlemail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=skumark1902@gmail.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