From: Greg KH <gregkh@linuxfoundation.org>
To: Baokun Li <libaokun1@huawei.com>
Cc: stable@vger.kernel.org, sashal@kernel.org, tytso@mit.edu,
jack@suse.cz, ritesh.list@gmail.com, patches@lists.linux.dev,
yangerkun@huawei.com
Subject: Re: [PATCH 5.15 1/3] ext4: add two helper functions extent_logical_end() and pa_logical_end()
Date: Tue, 31 Oct 2023 15:11:38 +0100 [thread overview]
Message-ID: <2023103129-variably-surfboard-d608@gregkh> (raw)
In-Reply-To: <e8b4cdee-55ad-647f-e209-db0c8ed07c3f@huawei.com>
On Tue, Oct 31, 2023 at 09:17:23PM +0800, Baokun Li wrote:
> On 2023/10/31 20:51, Greg KH wrote:
> > On Sat, Oct 28, 2023 at 02:47:47PM +0800, Baokun Li wrote:
> > > commit 43bbddc067883d94de7a43d5756a295439fbe37d upstream.
> > Why just 5.15 and older? What about 6.1.y? We can't take patches only
> > for older stable kernels, otherwise you will have a regression when you
> > upgrade. Please send a series for 6.1.y if you wish to have us apply
> > these for older kernels.
> Since this series of patches for 5.15 also applies to 6.1.y, sorry for not
> clarifying this.
Ok, thanks, now queued up.
greg k-h
next prev parent reply other threads:[~2023-10-31 14:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-28 6:47 [PATCH 5.15 1/3] ext4: add two helper functions extent_logical_end() and pa_logical_end() Baokun Li
2023-10-28 6:47 ` [PATCH 5.15 2/3] ext4: fix BUG in ext4_mb_new_inode_pa() due to overflow Baokun Li
2023-10-28 6:47 ` [PATCH 5.15 3/3] ext4: avoid overlapping preallocations " Baokun Li
2023-10-31 12:51 ` [PATCH 5.15 1/3] ext4: add two helper functions extent_logical_end() and pa_logical_end() Greg KH
2023-10-31 13:17 ` Baokun Li
2023-10-31 14:11 ` Greg KH [this message]
2023-11-01 1:47 ` Baokun Li
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=2023103129-variably-surfboard-d608@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=libaokun1@huawei.com \
--cc=patches@lists.linux.dev \
--cc=ritesh.list@gmail.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=yangerkun@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