From: Jan Kara <jack@suse.cz>
To: Liu Song <fishland@aliyun.com>
Cc: tytso@mit.edu, jack@suse.com, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, liu.song11@zte.com.cn
Subject: Re: [PATCH] jbd2: jbd2_get_transaction does not need to return a value
Date: Tue, 26 Feb 2019 17:35:04 +0100 [thread overview]
Message-ID: <20190226163504.GA24711@quack2.suse.cz> (raw)
In-Reply-To: <20190226160728.38587-1-fishland@aliyun.com>
On Wed 27-02-19 00:07:27, Liu Song wrote:
> In jbd2_get_transaction, a new transaction is initialized,
> and set to the j_running_transaction. No need for a return
> value, so remove it.
> Also, adjust some comments to match the actual operation
> of this function.
>
> Signed-off-by: Liu Song <liu.song11@zte.com.cn>
Looks good. You can add:
Reviewed-by: Jan Kara <jack@suse.cz>
Honza
> ---
> fs/jbd2/transaction.c | 8 +++-----
> 1 file changed, 3 insertions(+), 5 deletions(-)
>
> diff --git a/fs/jbd2/transaction.c b/fs/jbd2/transaction.c
> index cc35537232f2..79a028a7a579 100644
> --- a/fs/jbd2/transaction.c
> +++ b/fs/jbd2/transaction.c
> @@ -63,7 +63,7 @@ void jbd2_journal_free_transaction(transaction_t *transaction)
> /*
> * jbd2_get_transaction: obtain a new transaction_t object.
> *
> - * Simply allocate and initialise a new transaction. Create it in
> + * Simply initialise a new transaction. Initialize it in
> * RUNNING state and add it to the current journal (which should not
> * have an existing running transaction: we only make a new transaction
> * once we have started to commit the old one).
> @@ -75,8 +75,8 @@ void jbd2_journal_free_transaction(transaction_t *transaction)
> *
> */
>
> -static transaction_t *
> -jbd2_get_transaction(journal_t *journal, transaction_t *transaction)
> +static void jbd2_get_transaction(journal_t *journal,
> + transaction_t *transaction)
> {
> transaction->t_journal = journal;
> transaction->t_state = T_RUNNING;
> @@ -100,8 +100,6 @@ jbd2_get_transaction(journal_t *journal, transaction_t *transaction)
> transaction->t_max_wait = 0;
> transaction->t_start = jiffies;
> transaction->t_requested = 0;
> -
> - return transaction;
> }
>
> /*
> --
> 2.19.1
>
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next parent reply other threads:[~2019-02-26 16:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190226160728.38587-1-fishland@aliyun.com>
2019-02-26 16:35 ` Jan Kara [this message]
2019-03-01 5:39 ` 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=20190226163504.GA24711@quack2.suse.cz \
--to=jack@suse.cz \
--cc=fishland@aliyun.com \
--cc=jack@suse.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liu.song11@zte.com.cn \
--cc=tytso@mit.edu \
/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
Powered by JetHome