public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Carlos Llamas <cmllamas@google.com>
To: Kuan-Wei Chiu <visitorckw@gmail.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] binderfs: fix typo in binderfs.c
Date: Tue, 5 Sep 2023 17:19:45 +0000	[thread overview]
Message-ID: <ZPdjMXdDBxYRwNA7@google.com> (raw)
In-Reply-To: <20230903204250.2697370-1-visitorckw@gmail.com>

On Mon, Sep 04, 2023 at 04:42:50AM +0800, Kuan-Wei Chiu wrote:
> The word "wich"
> was corrected to "which" for spelling accuracy.
> 
> Signed-off-by: Kuan-Wei Chiu <visitorckw@gmail.com>
> ---
>  drivers/android/binderfs.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/android/binderfs.c b/drivers/android/binderfs.c
> index 81effec17b3d..ae2a8413ec12 100644
> --- a/drivers/android/binderfs.c
> +++ b/drivers/android/binderfs.c
> @@ -93,7 +93,7 @@ bool is_binderfs_device(const struct inode *inode)
>  /**
>   * binderfs_binder_device_create - allocate inode from super block of a
>   *                                 binderfs mount
> - * @ref_inode: inode from wich the super block will be taken
> + * @ref_inode: inode from which the super block will be taken
>   * @userp:     buffer to copy information about new device for userspace to
>   * @req:       struct binderfs_device as copied from userspace
>   *
> -- 
> 2.25.1
> 

Thanks,

Acked-by: Carlos Llamas <cmllamas@google.com>

      reply	other threads:[~2023-09-05 17:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-03 20:42 [PATCH] binderfs: fix typo in binderfs.c Kuan-Wei Chiu
2023-09-05 17:19 ` 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=ZPdjMXdDBxYRwNA7@google.com \
    --to=cmllamas@google.com \
    --cc=arve@android.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 \
    --cc=visitorckw@gmail.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