From: Jan Kara <jack@suse.cz>
To: wangyan <wangyan122@huawei.com>
Cc: tytso@mit.edu, jack@suse.com, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] jbd2: delete the duplicated words in the comments
Date: Wed, 22 Jan 2020 10:48:26 +0100 [thread overview]
Message-ID: <20200122094826.GD12845@quack2.suse.cz> (raw)
In-Reply-To: <12087f77-ab4d-c7ba-53b4-893dbf0026f0@huawei.com>
On Wed 22-01-20 17:33:10, wangyan wrote:
> Delete the duplicated words "is" in the comments
>
> Signed-off-by: Yan Wang <wangyan122@huawei.com>
Looks good. Thanks. You can add:
Reviewed-by: Jan Kara <jack@suse.cz>
Honza
> ---
> fs/jbd2/transaction.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/jbd2/transaction.c b/fs/jbd2/transaction.c
> index 27b9f9dee434..5c3abbaccb57 100644
> --- a/fs/jbd2/transaction.c
> +++ b/fs/jbd2/transaction.c
> @@ -525,7 +525,7 @@ EXPORT_SYMBOL(jbd2__journal_start);
> * modified buffers in the log. We block until the log can guarantee
> * that much space. Additionally, if rsv_blocks > 0, we also create another
> * handle with rsv_blocks reserved blocks in the journal. This handle is
> - * is stored in h_rsv_handle. It is not attached to any particular transaction
> + * stored in h_rsv_handle. It is not attached to any particular transaction
> * and thus doesn't block transaction commit. If the caller uses this reserved
> * handle, it has to set h_rsv_handle to NULL as otherwise jbd2_journal_stop()
> * on the parent handle will dispose the reserved one. Reserved handle has to
> --
> 2.19.1
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2020-01-22 9:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 9:33 [PATCH] jbd2: delete the duplicated words in the comments wangyan
2020-01-22 9:48 ` Jan Kara [this message]
2020-01-25 7:23 ` Theodore Y. Ts'o
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=20200122094826.GD12845@quack2.suse.cz \
--to=jack@suse.cz \
--cc=jack@suse.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=wangyan122@huawei.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