From: Joseph Qi <jiangqi903@gmail.com>
To: ChenGang <cg.chen@huawei.com>, mark@fasheh.com, jlbec@evilplan.org
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
ocfs2-devel@oss.oracle.com,
"joseph.qi@linux.alibaba.com" <joseph.qi@linux.alibaba.com>
Subject: Re: [PATCH] fs: ocfs: fix spelling mistake "heartbeart" -> "heartbeat"
Date: Sun, 28 Apr 2019 01:32:05 +0000 [thread overview]
Message-ID: <cee2552d-3a57-418b-1c17-91bb714370f1@gmail.com> (raw)
In-Reply-To: <1556367755-118120-1-git-send-email-cg.chen@huawei.com>
Hi ChenGang,
Could you please fold these four patches into one?
Thanks,
Joseph
On 19/4/27 20:22, ChenGang wrote:
> There is a spelling mistake in o2hb_do_disk_heartbeat debug message.Fix it.
>
> Signed-off-by: ChenGang <cg.chen@huawei.com>
> ---
> fs/ocfs2/cluster/heartbeat.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/ocfs2/cluster/heartbeat.c b/fs/ocfs2/cluster/heartbeat.c
> index f3c20b2..e4e7df1 100644
> --- a/fs/ocfs2/cluster/heartbeat.c
> +++ b/fs/ocfs2/cluster/heartbeat.c
> @@ -1198,7 +1198,7 @@ static int o2hb_do_disk_heartbeat(struct o2hb_region *reg)
> if (atomic_read(®->hr_steady_iterations) != 0) {
> if (atomic_dec_and_test(®->hr_unsteady_iterations)) {
> printk(KERN_NOTICE "o2hb: Unable to stabilize "
> - "heartbeart on region %s (%s)\n",
> + "heartbeat on region %s (%s)\n",
> config_item_name(®->hr_item),
> reg->hr_dev_name);
> atomic_set(®->hr_steady_iterations, 0);
>
next prev parent reply other threads:[~2019-04-28 1:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-27 12:22 [PATCH] fs: ocfs: fix spelling mistake "heartbeart" -> "heartbeat" ChenGang
2019-04-28 1:32 ` Joseph Qi [this message]
2019-04-29 12:41 ` [PATCH] fs: ocfs: fix spelling mistake "hearbeating" " ChenGang
2019-04-30 1:31 ` Joseph Qi
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=cee2552d-3a57-418b-1c17-91bb714370f1@gmail.com \
--to=jiangqi903@gmail.com \
--cc=cg.chen@huawei.com \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--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