From: Ross Zwisler <zwisler@google.com>
To: Joseph Qi <joseph.qi@linux.alibaba.com>
Cc: akpm@linux-foundation.org, Theodore Ts'o <tytso@mit.edu>,
Ross Zwisler <zwisler@chromium.org>,
linux-ext4@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: Re: [PATCH 2/2] jbd2: remove jbd2_journal_inode_add_[write|wait]
Date: Fri, 12 Jul 2019 15:14:02 -0600 [thread overview]
Message-ID: <20190712211402.GA244046@google.com> (raw)
In-Reply-To: <1562914972-97318-2-git-send-email-joseph.qi@linux.alibaba.com>
On Fri, Jul 12, 2019 at 03:02:52PM +0800, Joseph Qi wrote:
> Since ext4/ocfs2 are using jbd2_inode dirty range scoping APIs now,
> jbd2_journal_inode_add_[write|wait] are not used any more, remove them.
>
> Signed-off-by: Joseph Qi <joseph.qi@linux.alibaba.com>
This looks correct to me. You can add:
Reviewed-by: Ross Zwisler <zwisler@google.com>
next prev parent reply other threads:[~2019-07-12 21:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 7:02 [PATCH 1/2] ocfs2: use jbd2_inode dirty range scoping Joseph Qi
2019-07-12 7:02 ` [Ocfs2-devel] " Joseph Qi
2019-07-12 7:02 ` [PATCH 2/2] jbd2: remove jbd2_journal_inode_add_[write|wait] Joseph Qi
2019-07-12 7:02 ` [Ocfs2-devel] " Joseph Qi
2019-07-12 21:14 ` Ross Zwisler [this message]
2019-07-12 9:45 ` [PATCH 1/2] ocfs2: use jbd2_inode dirty range scoping Changwei Ge
2019-07-12 9:45 ` [Ocfs2-devel] " Changwei Ge
2019-07-12 13:32 ` Joseph Qi
2019-07-12 13:32 ` [Ocfs2-devel] " Joseph Qi
2019-07-12 21:39 ` Ross Zwisler
-- strict thread matches above, loose matches on Subject: below --
2019-07-13 0:26 Joseph Qi
2019-07-13 0:26 ` [PATCH 2/2] jbd2: remove jbd2_journal_inode_add_[write|wait] Joseph Qi
2019-07-15 3:44 ` Changwei Ge
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=20190712211402.GA244046@google.com \
--to=zwisler@google.com \
--cc=akpm@linux-foundation.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-ext4@vger.kernel.org \
--cc=ocfs2-devel@oss.oracle.com \
--cc=tytso@mit.edu \
--cc=zwisler@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.