From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
akpm@linux-foundation.org, Mark Fasheh <mark@fasheh.com>,
Joel Becker <jlbec@evilplan.org>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
ocfs2-devel@oss.oracle.com
Subject: Re: [PATCH v2 3/3] ocfs2: Fix a typo in a comment
Date: Fri, 22 Jul 2022 09:33:22 +0800 [thread overview]
Message-ID: <9e8b39ec-bfda-2e60-2626-f55ec95bd268@linux.alibaba.com> (raw)
In-Reply-To: <4d4a6786e8ad522bfad6d2401b7f6634f8af0e5d.1658436259.git.christophe.jaillet@wanadoo.fr>
On 7/22/22 4:49 AM, Christophe JAILLET wrote:
> s/heartbaet/heartbeat
>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Reviewed-by: Joseph Qi <joseph.qi@linux.alibaba.com>
> ---
> v1 -> v2
> - this patch is new in the serie
> ---
> fs/ocfs2/heartbeat.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/ocfs2/heartbeat.c b/fs/ocfs2/heartbeat.c
> index dd29d60af154..22da768e65b7 100644
> --- a/fs/ocfs2/heartbeat.c
> +++ b/fs/ocfs2/heartbeat.c
> @@ -2,7 +2,7 @@
> /*
> * heartbeat.c
> *
> - * Register ourselves with the heartbaet service, keep our node maps
> + * Register ourselves with the heartbeat service, keep our node maps
> * up to date, and fire off recovery when needed.
> *
> * Copyright (C) 2002, 2004 Oracle. All rights reserved.
prev parent reply other threads:[~2022-07-22 1:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 20:49 [PATCH v2 0/3] ocfs2: A few clean_ups Christophe JAILLET
2022-07-21 20:49 ` [PATCH v2 1/3] ocfs2: Remove some useless functions Christophe JAILLET
2022-07-21 20:49 ` [PATCH v2 2/3] ocfs2: use the bitmap API to simplify code Christophe JAILLET
2022-07-21 20:49 ` [PATCH v2 3/3] ocfs2: Fix a typo in a comment Christophe JAILLET
2022-07-22 1:33 ` Joseph Qi [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=9e8b39ec-bfda-2e60-2626-f55ec95bd268@linux.alibaba.com \
--to=joseph.qi@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=jlbec@evilplan.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@oss.oracle.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
all inboxes | Powered by JetHome®