From: Mukesh Ojha <quic_mojha@quicinc.com>
To: Kemeng Shi <shikemeng@huawei.com>, <tj@kernel.org>, <axboe@kernel.dk>
Cc: <cgroups@vger.kernel.org>, <linux-block@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] blk-cgroup: Fix typo in comment
Date: Thu, 13 Oct 2022 19:49:22 +0530 [thread overview]
Message-ID: <9662bcef-f901-fac6-1dff-dc2a2da216fe@quicinc.com> (raw)
In-Reply-To: <20221013141659.24032-1-shikemeng@huawei.com>
Hi,
On 10/13/2022 7:46 PM, Kemeng Shi wrote:
> Replace assocating with associating.
> Replace intiailized with initialized.
>
> Signed-off-by: Kemeng Shi <shikemeng@huawei.com>
> Acked-by: Tejun Heo <tj@kernel.org>
> ---
> Changes in v2:
> -based on current mainline code
> -add acked-by
>
> block/blk-cgroup.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/block/blk-cgroup.c b/block/blk-cgroup.c
> index 6a5c849ee061..4c4bc874bd95 100644
> --- a/block/blk-cgroup.c
> +++ b/block/blk-cgroup.c
> @@ -577,7 +577,7 @@ EXPORT_SYMBOL_GPL(blkcg_print_blkgs);
> * @pd: policy private data of interest
> * @v: value to print
> *
> - * Print @v to @sf for the device assocaited with @pd.
> + * Print @v to @sf for the device associated with @pd.
> */
> u64 __blkg_prfill_u64(struct seq_file *sf, struct blkg_policy_data *pd, u64 v)
> {
> @@ -765,7 +765,7 @@ EXPORT_SYMBOL_GPL(blkg_conf_prep);
>
> /**
> * blkg_conf_finish - finish up per-blkg config update
> - * @ctx: blkg_conf_ctx intiailized by blkg_conf_prep()
> + * @ctx: blkg_conf_ctx initialized by blkg_conf_prep()
> *
> * Finish up after per-blkg config update. This function must be paired
> * with blkg_conf_prep().
LGTM.
Reviewed-by: Mukesh Ojha <quic_mojha@quicinc.com>
-Mukesh
next prev parent reply other threads:[~2022-10-13 14:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 14:16 Kemeng Shi
2022-10-13 14:19 ` Mukesh Ojha [this message]
2022-11-23 6:07 ` Kemeng Shi
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=9662bcef-f901-fac6-1dff-dc2a2da216fe@quicinc.com \
--to=quic_mojha@quicinc.com \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shikemeng@huawei.com \
--cc=tj@kernel.org \
/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
all inboxes | Powered by JetHome®