ceph-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ilya Dryomov <idryomov@gmail.com>
To: Lu Wei <luwei32@huawei.com>
Cc: Jeff Layton <jlayton@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	Ceph Development <ceph-devel@vger.kernel.org>,
	netdev <netdev@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	xiyou.wangcong@gmail.com, ap420073@gmail.com,
	linux-decnet-user@lists.sourceforge.net,
	Andrew Lunn <andrew@lunn.ch>,
	vivien.didelot@gmail.com, Florian Fainelli <f.fainelli@gmail.com>,
	olteanv@gmail.com, steffen.klassert@secunet.com,
	Herbert Xu <herbert@gondor.apana.org.au>,
	yoshfuji@linux-ipv6.org, dsahern@kernel.org
Subject: Re: [PATCH -next 1/5] net: ceph: Fix a typo in osdmap.c
Date: Thu, 25 Mar 2021 17:41:16 +0100	[thread overview]
Message-ID: <CAOi1vP9uuaY9OMmW0Xni5iUztyAviFH3N11ohWbb2zqXsGYMiQ@mail.gmail.com> (raw)
In-Reply-To: <20210325063825.228167-2-luwei32@huawei.com>

On Thu, Mar 25, 2021 at 7:37 AM Lu Wei <luwei32@huawei.com> wrote:
>
> Modify "inital" to "initial" in net/ceph/osdmap.c.
>
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: Lu Wei <luwei32@huawei.com>
> ---
>  net/ceph/osdmap.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/ceph/osdmap.c b/net/ceph/osdmap.c
> index 2b1dd252f231..c959320c4775 100644
> --- a/net/ceph/osdmap.c
> +++ b/net/ceph/osdmap.c
> @@ -1069,7 +1069,7 @@ static struct crush_work *get_workspace(struct workspace_manager *wsm,
>
>                 /*
>                  * Do not return the error but go back to waiting.  We
> -                * have the inital workspace and the CRUSH computation
> +                * have the initial workspace and the CRUSH computation
>                  * time is bounded so we will get it eventually.
>                  */
>                 WARN_ON(atomic_read(&wsm->total_ws) < 1);
> --
> 2.17.1
>

Hi Lu,

There is at least one other legit typo in that file: "ambigous".
I'd rather fix all typos at once, so curious why Hulk Robot didn't
catch it.

Thanks,

                Ilya

  reply	other threads:[~2021-03-25 16:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-25  6:38 [PATCH -next 0/5]Fix some typos Lu Wei
2021-03-25  6:38 ` [PATCH -next 1/5] net: ceph: Fix a typo in osdmap.c Lu Wei
2021-03-25 16:41   ` Ilya Dryomov [this message]
2021-03-25  6:38 ` [PATCH -next 2/5] net: core: Fix a typo in dev_addr_lists.c Lu Wei
2021-03-25  6:38 ` [PATCH -next 3/5] net: decnet: Fix a typo in dn_nsp_in.c Lu Wei
2021-03-25  6:38 ` [PATCH -next 4/5] net: dsa: Fix a typo in tag_rtl4_a.c Lu Wei
2021-03-25  6:38 ` [PATCH -next 5/5] net: ipv4: Fix some typos Lu Wei
2021-03-26  0:20 ` [PATCH -next 0/5]Fix " patchwork-bot+netdevbpf

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=CAOi1vP9uuaY9OMmW0Xni5iUztyAviFH3N11ohWbb2zqXsGYMiQ@mail.gmail.com \
    --to=idryomov@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=ap420073@gmail.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=jlayton@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-decnet-user@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luwei32@huawei.com \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=steffen.klassert@secunet.com \
    --cc=vivien.didelot@gmail.com \
    --cc=xiyou.wangcong@gmail.com \
    --cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).