From: Jan Kara <jack@suse.cz>
To: Zhihao Cheng <chengzhihao1@huawei.com>
Cc: tytso@mit.edu, adilger.kernel@dilger.ca, jack@suse.com,
tudor.ambarus@linaro.org, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, yi.zhang@huawei.com
Subject: Re: [PATCH v2 2/5] jbd2: remove unused feature macros
Date: Tue, 14 Mar 2023 12:35:04 +0100 [thread overview]
Message-ID: <20230314113504.xfo7q2uy6q623vzb@quack3> (raw)
In-Reply-To: <20230313132021.672134-3-chengzhihao1@huawei.com>
On Mon 13-03-23 21:20:18, Zhihao Cheng wrote:
> From: Zhang Yi <yi.zhang@huawei.com>
>
> JBD2_HAS_[IN|RO_]COMPAT_FEATURE macros are no longer used, just remove
> them.
>
> Signed-off-by: Zhang Yi <yi.zhang@huawei.com>
> Signed-off-by: Zhihao Cheng <chengzhihao1@huawei.com>
I gave you my Reviewed-by on this patch (and a few others in this series).
Why didn't you include it?
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2023-03-14 11:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 13:20 [PATCH v2 0/5] ext4: Fix stale buffer loading from last failed Zhihao Cheng
2023-03-13 13:20 ` [PATCH v2 1/5] ext4: Fix reusing stale buffer heads from last failed mounting Zhihao Cheng
2023-03-14 11:33 ` Jan Kara
2023-03-14 12:01 ` Zhihao Cheng
2023-03-14 12:11 ` Jan Kara
2023-03-14 12:31 ` Zhihao Cheng
2023-03-14 14:28 ` Jan Kara
2023-03-14 14:37 ` Zhihao Cheng
2023-03-13 13:20 ` [PATCH v2 2/5] jbd2: remove unused feature macros Zhihao Cheng
2023-03-14 11:35 ` Jan Kara [this message]
2023-03-14 12:02 ` Zhihao Cheng
2023-03-13 13:20 ` [PATCH v2 3/5] jbd2: switch to check format version in superblock directly Zhihao Cheng
2023-03-13 13:20 ` [PATCH v2 4/5] jbd2: factor out journal initialization from journal_get_superblock() Zhihao Cheng
2023-03-13 13:20 ` [PATCH v2 5/5] jbd2: remove j_format_version Zhihao Cheng
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=20230314113504.xfo7q2uy6q623vzb@quack3 \
--to=jack@suse.cz \
--cc=adilger.kernel@dilger.ca \
--cc=chengzhihao1@huawei.com \
--cc=jack@suse.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tudor.ambarus@linaro.org \
--cc=tytso@mit.edu \
--cc=yi.zhang@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