Outreachy Linux Kernel Community
 help / color / mirror / Atom feed
From: Tahera Fahimi <fahimitahera@gmail.com>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: gregkh@linuxfoundation.org, outreachy@lists.linux.dev
Subject: Re: [PATCH] staging: ks7010: fix spinlock_t definition without comment
Date: Tue, 12 Mar 2024 17:29:51 -0600	[thread overview]
Message-ID: <ZfDlbwCtgdEBOlbp@tahera-OptiPlex-5000> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2403122247530.3229@hadrien>

On Tue, Mar 12, 2024 at 10:49:58PM +0100, Julia Lawall wrote:
> 
> 
> On Tue, 12 Mar 2024, TaheraFahimi wrote:
> 
> > This change ensures adherence to coding style guidelines.
> >
> > 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 3e9a91b5131c..94322e2ea304 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 */
> 
> How did you come up with this comment?  I'm not sure that it reflects very
> well the function in which the lock is used.
> 
> julia
> 
> >  	spinlock_t dev_read_lock;
> >  	wait_queue_head_t devread_wait;
> >
> > --
> > 2.34.1
> >
> >
> >
I came up with this comment since this lock is used in function "devio_rec_ind" in ks_hostif.c to ensure safe access to the device's receive buffer.

  reply	other threads:[~2024-03-12 23:29 UTC|newest]

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

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=ZfDlbwCtgdEBOlbp@tahera-OptiPlex-5000 \
    --to=fahimitahera@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=julia.lawall@inria.fr \
    --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