linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Manivannan Sadhasivam <mani@kernel.org>
To: Jarvis Jiang <jarvis.w.jiang@gmail.com>
Cc: hemantk@codeaurora.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, cchen50@lenovo.com,
	mpearson@lenovo.com
Subject: Re: [PATCH 2/2] bus: mhi: fix typo in comments for struct mhi_channel_config
Date: Fri, 9 Apr 2021 19:29:43 +0530	[thread overview]
Message-ID: <20210409135943.GE31856@work> (raw)
In-Reply-To: <20210408100220.3853-1-jarvis.w.jiang@gmail.com>

On Thu, Apr 08, 2021 at 03:02:20AM -0700, Jarvis Jiang wrote:
> The word 'rung' is a typo in below comment, fix it.
> * @event_ring: The event rung index that services this channel
> 
> Signed-off-by: Jarvis Jiang <jarvis.w.jiang@gmail.com>

Applied to mhi-next!

Thanks,
Mani

> ---
>  include/linux/mhi.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/linux/mhi.h b/include/linux/mhi.h
> index d095fba37d1e..944aa3aa3035 100644
> --- a/include/linux/mhi.h
> +++ b/include/linux/mhi.h
> @@ -205,7 +205,7 @@ enum mhi_db_brst_mode {
>   * @num: The number assigned to this channel
>   * @num_elements: The number of elements that can be queued to this channel
>   * @local_elements: The local ring length of the channel
> - * @event_ring: The event rung index that services this channel
> + * @event_ring: The event ring index that services this channel
>   * @dir: Direction that data may flow on this channel
>   * @type: Channel type
>   * @ee_mask: Execution Environment mask for this channel
> -- 
> 2.25.1
> 

      parent reply	other threads:[~2021-04-09 13:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-08 10:02 [PATCH 2/2] bus: mhi: fix typo in comments for struct mhi_channel_config Jarvis Jiang
2021-04-09 13:17 ` Manivannan Sadhasivam
2021-04-09 13:59 ` Manivannan Sadhasivam [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=20210409135943.GE31856@work \
    --to=mani@kernel.org \
    --cc=cchen50@lenovo.com \
    --cc=hemantk@codeaurora.org \
    --cc=jarvis.w.jiang@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpearson@lenovo.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;
as well as URLs for NNTP newsgroup(s).