From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: Zhihao Cheng <chengzhihao1@huawei.com>,
tytso@mit.edu, adilger.kernel@dilger.ca, jack@suse.com
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
yi.zhang@huawei.com, Lee Jones <joneslee@google.com>
Subject: Re: [PATCH 1/5] ext4: Fix reusing stale buffer heads from last failed mounting
Date: Mon, 13 Mar 2023 12:43:37 +0000 [thread overview]
Message-ID: <d3f2cb4d-da47-baec-4d93-4f1a700a07d3@linaro.org> (raw)
In-Reply-To: <20230310125206.2867822-2-chengzhihao1@huawei.com>
Hi, Zhihao,
On 3/10/23 12:52, Zhihao Cheng wrote:
cut
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=217171
> Cc: <stable@kernel.org>
Shouldn't have been stable@vger.kernel.org instead? That's what is
advertised at:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
A Fixes tag would be helpful. It would assist the stable kernel team, or
people that have to backport your patch, in determining which stable
versions should receive your fix. Same suggestion is made in
https://www.kernel.org/doc/html/latest/process/submitting-patches.html
Thanks!
ta
next prev parent reply other threads:[~2023-03-13 12:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 12:52 [PATCH 0/5] ext4: Fix stale buffer loading from last failed Zhihao Cheng
2023-03-10 12:52 ` [PATCH 1/5] ext4: Fix reusing stale buffer heads from last failed mounting Zhihao Cheng
2023-03-13 10:51 ` Jan Kara
2023-03-13 12:43 ` Tudor Ambarus [this message]
2023-03-10 12:52 ` [PATCH 2/5] jbd2: remove unused feature macros Zhihao Cheng
2023-03-13 10:52 ` Jan Kara
2023-03-10 12:52 ` [PATCH 3/5] jbd2: switch to check format version in superblock directly Zhihao Cheng
2023-03-13 10:57 ` Jan Kara
2023-03-10 12:52 ` [PATCH 4/5] jbd2: factor out journal initialization from journal_get_superblock() Zhihao Cheng
2023-03-13 11:12 ` Jan Kara
2023-03-13 12:48 ` Zhang Yi
2023-03-10 12:52 ` [PATCH 5/5] jbd2: remove j_format_version Zhihao Cheng
2023-03-13 11:13 ` Jan Kara
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=d3f2cb4d-da47-baec-4d93-4f1a700a07d3@linaro.org \
--to=tudor.ambarus@linaro.org \
--cc=adilger.kernel@dilger.ca \
--cc=chengzhihao1@huawei.com \
--cc=jack@suse.com \
--cc=joneslee@google.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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