From: "Theodore Ts'o" <tytso@mit.edu>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: zhangshida <starzhangzsd@gmail.com>,
stable@vger.kernel.org, Shida Zhang <zhangshida@kylinos.cn>,
stable@kernel.org, Andreas Dilger <adilger@dilger.ca>,
"Darrick J . Wong" <djwong@kernel.org>
Subject: Re: [PATCH] ext4: fix rec_len verify error
Date: Fri, 22 Sep 2023 11:11:36 -0400 [thread overview]
Message-ID: <ZQ2uqEO51hJI4RRi@mit.edu> (raw)
In-Reply-To: <2023092232-squash-buggy-51c7@gregkh>
On Fri, Sep 22, 2023 at 11:23:59AM +0200, Greg KH wrote:
>
> What stable tree(s) are you asking this to be backported to?
I assume that from the reply to message id
2023092057-company-unworried-210b@gregkh, this was intended for the
4.14 stable tree (since the automatic backport didn't apply).
Zhangshida, for future reference, when sending a patch for an LTS
kernel, please include the kernel version in the PATCH line,
e.g. "[PATCH 4.14.123]" or some such. This saves everyone a lot of
time (including myself, since I need to filter out the LTS backports
to ext4 patchwork dashboard).
Thanks,
- Ted
next prev parent reply other threads:[~2023-09-22 15:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 9:58 FAILED: patch "[PATCH] ext4: fix rec_len verify error" failed to apply to 4.14-stable tree gregkh
2023-09-22 5:39 ` [PATCH] ext4: fix rec_len verify error zhangshida
2023-09-22 9:23 ` Greg KH
2023-09-22 15:11 ` Theodore Ts'o [this message]
2023-09-24 2:19 ` [PATCH 4.14.y] " zhangshida
2023-10-07 10:19 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2023-09-20 9:58 FAILED: patch "[PATCH] ext4: fix rec_len verify error" failed to apply to 4.19-stable tree gregkh
2023-09-22 2:54 ` [PATCH] ext4: fix rec_len verify error zhangshida
2023-09-22 9:27 ` Greg KH
2023-09-23 9:41 ` Stephen Zhang
2023-09-23 14:47 ` Theodore Ts'o
2023-09-23 16:10 ` Greg KH
2023-07-29 6:13 [PATCH] ext4: Fix " zhangshida
2023-07-29 19:09 ` Andreas Dilger
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=ZQ2uqEO51hJI4RRi@mit.edu \
--to=tytso@mit.edu \
--cc=adilger@dilger.ca \
--cc=djwong@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=stable@kernel.org \
--cc=stable@vger.kernel.org \
--cc=starzhangzsd@gmail.com \
--cc=zhangshida@kylinos.cn \
/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.