From: Joseph Qi <jiangqi903@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Cc: ocfs2-devel@oss.oracle.com, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [Ocfs2-devel] [PATCH] ocfs2: suballoc.h: delete a duplicated word
Date: Mon, 20 Jul 2020 09:17:22 +0800 [thread overview]
Message-ID: <540ab401-d7a3-1b94-7acf-3852ce2292b7@gmail.com> (raw)
In-Reply-To: <20200720001421.28823-1-rdunlap@infradead.org>
On 2020/7/20 08:14, Randy Dunlap wrote:
> Drop the repeated word "is" in a comment.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Mark Fasheh <mark@fasheh.com>
> Cc: Joel Becker <jlbec@evilplan.org>
> Cc: Joseph Qi <joseph.qi@linux.alibaba.com>
> Cc: ocfs2-devel@oss.oracle.com
Acked-by: Joseph Qi <joseph.qi@linux.alibaba.com>
> ---
> fs/ocfs2/suballoc.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- linux-next-20200717.orig/fs/ocfs2/suballoc.h
> +++ linux-next-20200717/fs/ocfs2/suballoc.h
> @@ -40,7 +40,7 @@ struct ocfs2_alloc_context {
>
> u64 ac_last_group;
> u64 ac_max_block; /* Highest block number to allocate. 0 is
> - is the same as ~0 - unlimited */
> + the same as ~0 - unlimited */
>
> int ac_find_loc_only; /* hack for reflink operation ordering */
> struct ocfs2_suballoc_result *ac_find_loc_priv; /* */
>
> _______________________________________________
> Ocfs2-devel mailing list
> Ocfs2-devel@oss.oracle.com
> https://oss.oracle.com/mailman/listinfo/ocfs2-devel
>
prev parent reply other threads:[~2020-07-20 1:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 0:14 [PATCH] ocfs2: suballoc.h: delete a duplicated word Randy Dunlap
2020-07-20 1:17 ` 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=540ab401-d7a3-1b94-7acf-3852ce2292b7@gmail.com \
--to=jiangqi903@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ocfs2-devel@oss.oracle.com \
--cc=rdunlap@infradead.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).