public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Ajith P V <ajithpv.linux@gmail.com>
Cc: arve@android.com, tkjos@android.com, maco@android.com,
	joel@joelfernandes.org, christian@brauner.io, hridya@google.com,
	surenb@google.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] binder: remove repeat word from comment to avoid warning
Date: Thu, 30 Dec 2021 14:12:04 +0100	[thread overview]
Message-ID: <Yc2wJOa4fLKm4uoV@kroah.com> (raw)
In-Reply-To: <20211223122725.29842-1-ajithpv.linux@gmail.com>

On Thu, Dec 23, 2021 at 05:57:25PM +0530, Ajith P V wrote:
> binder.c file comment produce warning with checkpatch as below:
> WARNING: Possible repeated word: 'and'
> Remove the repeated word from the comment to avoid this warning.
> 
> Signed-off-by: Ajith P V <ajithpv.linux@gmail.com>
> ---
>  drivers/android/binder.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/android/binder.c b/drivers/android/binder.c
> index cffbe57a8e08..fc0f4e8b58bd 100644
> --- a/drivers/android/binder.c
> +++ b/drivers/android/binder.c
> @@ -4436,7 +4436,7 @@ static int binder_thread_release(struct binder_proc *proc,
>  
>  	/*
>  	 * This is needed to avoid races between wake_up_poll() above and
> -	 * and ep_remove_waitqueue() called for other reasons (eg the epoll file
> +	 * ep_remove_waitqueue() called for other reasons (eg the epoll file
>  	 * descriptor being closed); ep_remove_waitqueue() holds an RCU read
>  	 * lock, so we can be sure it's done after calling synchronize_rcu().
>  	 */
> -- 
> 2.17.1
> 

Does not apply to my tree at all :(

      reply	other threads:[~2021-12-30 13:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-23 12:27 [PATCH] binder: remove repeat word from comment to avoid warning Ajith P V
2021-12-30 13:12 ` 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=Yc2wJOa4fLKm4uoV@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ajithpv.linux@gmail.com \
    --cc=arve@android.com \
    --cc=christian@brauner.io \
    --cc=hridya@google.com \
    --cc=joel@joelfernandes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maco@android.com \
    --cc=surenb@google.com \
    --cc=tkjos@android.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