From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: Colin King <colin.king@canonical.com>,
Mark Fasheh <mark@fasheh.com>, Joel Becker <jlbec@evilplan.org>,
ocfs2-devel@oss.oracle.com,
Andrew Morton <akpm@linux-foundation.org>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ocfs2: fix spelling mistake "ambigous" -> "ambiguous"
Date: Thu, 12 Sep 2019 08:54:41 +0800 [thread overview]
Message-ID: <831bdff4-064e-038b-f45d-c4d265cbff1e@linux.alibaba.com> (raw)
In-Reply-To: <20190911160728.24322-1-colin.king@canonical.com>
On 19/9/12 00:07, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> There is a spelling mistake in a mlog_bug_on_msg message. Fix it.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Acked-by: Joseph Qi <joseph.qi@linux.alibaba.com>
> ---
> fs/ocfs2/inode.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/ocfs2/inode.c b/fs/ocfs2/inode.c
> index 7ad9d6590818..7c9dfd50c1c1 100644
> --- a/fs/ocfs2/inode.c
> +++ b/fs/ocfs2/inode.c
> @@ -534,7 +534,7 @@ static int ocfs2_read_locked_inode(struct inode *inode,
> */
> mlog_bug_on_msg(!!(fe->i_flags & cpu_to_le32(OCFS2_SYSTEM_FL)) !=
> !!(args->fi_flags & OCFS2_FI_FLAG_SYSFILE),
> - "Inode %llu: system file state is ambigous\n",
> + "Inode %llu: system file state is ambiguous\n",
> (unsigned long long)args->fi_blkno);
>
> if (S_ISCHR(le16_to_cpu(fe->i_mode)) ||
>
next prev parent reply other threads:[~2019-09-12 0:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 16:07 [PATCH] ocfs2: fix spelling mistake "ambigous" -> "ambiguous" Colin King
2019-09-12 0:54 ` Joseph Qi [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-08-03 14:09 [PATCH] ocfs2: fix spelling mistake: " Colin King
2018-04-27 18:57 Colin King
2017-06-28 15:45 Colin King
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=831bdff4-064e-038b-f45d-c4d265cbff1e@linux.alibaba.com \
--to=joseph.qi@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=colin.king@canonical.com \
--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;
as well as URLs for NNTP newsgroup(s).