Outreachy Linux Kernel Community
 help / color / mirror / Atom feed
From: Alison Schofield <alison.schofield@intel.com>
To: TaheraFahimi <fahimitahera@gmail.com>
Cc: outreachy@lists.linux.dev, gregkh@linuxfoundation.org
Subject: Re: [PATCH] staging: ks7010: fix spinlock_t definition without comment
Date: Wed, 20 Mar 2024 12:20:28 -0700	[thread overview]
Message-ID: <Zfs2/PXc9tiZFABx@aschofie-mobl2> (raw)
In-Reply-To: <ZfS7jcATb211X4I8@tahera-OptiPlex-5000>

On Fri, Mar 15, 2024 at 03:20:13PM -0600, TaheraFahimi wrote:

This has been discussed recently on the list -
https://lore.kernel.org/outreachy/ZfDHg49k0Og3z9Lw@tahera-OptiPlex-5000/


> Signed-off-by: TaheraFahimi <fahimitahera@gmail.com>
> ---
>  drivers/staging/ks7010/ks_wlan.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/staging/ks7010/ks_wlan.h b/drivers/staging/ks7010/ks_wlan.h
> index 94322e2ea304..bda7e0255b2c 100644
> --- a/drivers/staging/ks7010/ks_wlan.h
> +++ b/drivers/staging/ks7010/ks_wlan.h
> @@ -468,7 +468,7 @@ struct ks_wlan_private {
>  	char nick[IW_ESSID_MAX_SIZE + 1];
>  
>  	spinlock_t multicast_spin;
> -	/* lock for synchronize access to device read operation */
> +	/* lock to ensure safe access to the device's receive buffer */
>  	spinlock_t dev_read_lock;
>  	wait_queue_head_t devread_wait;
>  
> -- 
> 2.34.1
> 
> 

  reply	other threads:[~2024-03-20 19:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-15 21:20 [PATCH] staging: ks7010: fix spinlock_t definition without comment TaheraFahimi
2024-03-20 19:20 ` Alison Schofield [this message]
2024-03-20 19:22 ` Alison Schofield
  -- strict thread matches above, loose matches on Subject: below --
2024-03-12 21:22 TaheraFahimi
2024-03-12 21:49 ` Julia Lawall
2024-03-12 23:29   ` Tahera Fahimi
     [not found]   ` <ZfDdQDvGglrAX0Kq@tahera-OptiPlex-5000>
2024-03-13  6:40     ` Julia Lawall

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=Zfs2/PXc9tiZFABx@aschofie-mobl2 \
    --to=alison.schofield@intel.com \
    --cc=fahimitahera@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=outreachy@lists.linux.dev \
    /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