From: Carlos Llamas <cmllamas@google.com>
To: bajing <bajing@cmss.chinamobile.com>
Cc: gregkh@linuxfoundation.org, arve@android.com, tkjos@android.com,
maco@android.com, joel@joelfernandes.org, brauner@kernel.org,
surenb@google.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] android: binder: modify incorrect comments
Date: Sat, 31 Aug 2024 14:16:32 +0000 [thread overview]
Message-ID: <ZtMlwFZdMjgfgdOv@google.com> (raw)
In-Reply-To: <20240830073743.2052-1-bajing@cmss.chinamobile.com>
On Fri, Aug 30, 2024 at 03:37:43PM +0800, bajing wrote:
> The comment for binder_proc_unlock was incorrect, so it should be modified.
Can you specify why the comment is incorrect?
>
> Signed-off-by: bajing <bajing@cmss.chinamobile.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 fc55b5d0e4f3..578861d57045 100644
> --- a/drivers/android/binder.c
> +++ b/drivers/android/binder.c
> @@ -277,7 +277,7 @@ _binder_proc_lock(struct binder_proc *proc, int line)
> }
>
> /**
> - * binder_proc_unlock() - Release spinlock for given binder_proc
> + * binder_proc_unlock() - Release outer lock for given binder_proc
> * @proc: struct binder_proc to acquire
> *
> * Release lock acquired via binder_proc_lock()
> --
> 2.33.0
>
I'm ok with your change. It is specific about which spinlock it releases
(even though this is obvious from the code). It also pairs better with
the acquire comment block in binder_proc_lock().
However, you need to modify your commit message as the current comment
is technically _not_ incorrect. Can you please send a v2?
Thanks,
--
Carlos Llamas
prev parent reply other threads:[~2024-08-31 14:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 7:37 [PATCH] android: binder: modify incorrect comments bajing
2024-08-31 14:16 ` Carlos Llamas [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=ZtMlwFZdMjgfgdOv@google.com \
--to=cmllamas@google.com \
--cc=arve@android.com \
--cc=bajing@cmss.chinamobile.com \
--cc=brauner@kernel.org \
--cc=gregkh@linuxfoundation.org \
--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