ocfs2-devel.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Joseph Qi via Ocfs2-devel <ocfs2-devel@oss.oracle.com>
To: Jiangshan Yi <13667453960@163.com>,
	mark@fasheh.com, jlbec@evilplan.org,
	akpm <akpm@linux-foundation.org>
Cc: k2ci <kernel-bot@kylinos.cn>,
	linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com,
	Jiangshan Yi <yijiangshan@kylinos.cn>
Subject: Re: [Ocfs2-devel] [PATCH] fs/ocfs2/suballoc.h: fix spelling typo in comment
Date: Mon, 5 Sep 2022 16:04:11 +0800	[thread overview]
Message-ID: <e099ea78-cc1d-41d3-4ca7-99d5f723f440@linux.alibaba.com> (raw)
In-Reply-To: <20220905061656.1829179-1-13667453960@163.com>



On 9/5/22 2:16 PM, Jiangshan Yi wrote:
> From: Jiangshan Yi <yijiangshan@kylinos.cn>
> 
> Fix spelling typo in comment.
> 
> Reported-by: k2ci <kernel-bot@kylinos.cn>
> Signed-off-by: Jiangshan Yi <yijiangshan@kylinos.cn>

Acked-by: Joseph Qi <joseph.qi@linux.alibaba.com>
> ---
>  fs/ocfs2/suballoc.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/ocfs2/suballoc.h b/fs/ocfs2/suballoc.h
> index 5805a03d100b..9c74eace3adc 100644
> --- a/fs/ocfs2/suballoc.h
> +++ b/fs/ocfs2/suballoc.h
> @@ -106,7 +106,7 @@ int ocfs2_claim_clusters(handle_t *handle,
>  			 u32 *cluster_start,
>  			 u32 *num_clusters);
>  /*
> - * Use this variant of ocfs2_claim_clusters to specify a maxiumum
> + * Use this variant of ocfs2_claim_clusters to specify a maximum
>   * number of clusters smaller than the allocation reserved.
>   */
>  int __ocfs2_claim_clusters(handle_t *handle,

_______________________________________________
Ocfs2-devel mailing list
Ocfs2-devel@oss.oracle.com
https://oss.oracle.com/mailman/listinfo/ocfs2-devel

           reply	other threads:[~2022-09-05 13:17 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20220905061656.1829179-1-13667453960@163.com>]

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=e099ea78-cc1d-41d3-4ca7-99d5f723f440@linux.alibaba.com \
    --to=ocfs2-devel@oss.oracle.com \
    --cc=13667453960@163.com \
    --cc=akpm@linux-foundation.org \
    --cc=jlbec@evilplan.org \
    --cc=joseph.qi@linux.alibaba.com \
    --cc=kernel-bot@kylinos.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@fasheh.com \
    --cc=yijiangshan@kylinos.cn \
    /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).