All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jules Irenge <jbi.octave@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [PATCH] Fix spinlock_t definition without comment warning
Date: Mon, 11 Mar 2019 15:56:53 -0700	[thread overview]
Message-ID: <20190311225653.GA1008@kroah.com> (raw)
In-Reply-To: <20190309221810.25936-1-jbi.octave@gmail.com>

On Sat, Mar 09, 2019 at 10:18:10PM +0000, Jules Irenge wrote:
> Fix checkpatch issue: "CHECK: spinlock_t definition without comment".
> 
> Signed-off-by: Jules Irenge <jbi.octave@gmail.com>
> ---
>  drivers/staging/gdm724x/gdm_mux.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/staging/gdm724x/gdm_mux.h b/drivers/staging/gdm724x/gdm_mux.h
> index 51c22e3d8aeb..f1169d7e10c1 100644
> --- a/drivers/staging/gdm724x/gdm_mux.h
> +++ b/drivers/staging/gdm724x/gdm_mux.h
> @@ -60,7 +60,7 @@ struct rx_cxt {
>  	struct list_head to_host_list;
>  	struct list_head rx_submit_list;
>  	struct list_head rx_free_list;
> -	spinlock_t to_host_lock;
> +	spinlock_t to_host_lock; /* spinlock for to_host command handling */

Are you sure about this?  Please document why this is true somehow in
the changelog text so we feel good about it :)

Also, the subject: needs to be fixed up to show the subsystem (staging),
and the driver name.  See the other patches on the mailing list for the
proper format.

thanks,

greg k-h

>  	spinlock_t submit_list_lock;
>  	spinlock_t free_list_lock;
>  };
> -- 
> 2.20.1
> 


      reply	other threads:[~2019-03-11 22:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-09 22:18 [PATCH] Fix spinlock_t definition without comment warning Jules Irenge
2019-03-11 22:56 ` Greg KH [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=20190311225653.GA1008@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jbi.octave@gmail.com \
    --cc=outreachy-kernel@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.