From: Baokun Li <libaokun1@huawei.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: <linux-ext4@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<enwlinux@gmail.com>, <jack@suse.cz>, <lczerner@redhat.com>,
<yukuai3@huawei.com>, <yi.zhang@huawei.com>, <yebin10@huawei.com>,
<ritesh.list@gmail.com>, <adilger.kernel@dilger.ca>
Subject: Re: [PATCH 0/2] ext4: fix a infinite loop in do_writepages after online resizing
Date: Thu, 1 Dec 2022 14:26:21 +0800 [thread overview]
Message-ID: <faff95ef-7a4c-8176-4dac-aa1fb36d2bad@huawei.com> (raw)
In-Reply-To: <Y4gioFteBIg2WAEJ@mit.edu>
On 2022/12/1 11:42, Theodore Ts'o wrote:
> On Wed, Nov 30, 2022 at 10:08:13AM +0800, Baokun Li wrote:
>> But I thought this patch set was discarded because there was no
>> "Reviewed-by".
> No, it had just slipped through the cracks; and when I was going back
> through patchwork to see what patches were outstanding, I came across
> the patch set which had gotten missed during the last cycle; and I
> didn't notice that it had been superceded with a newer patch which
> achieved the same goal.
>
> I'll drop it from the ext4 tree and then pick up your newer series.
>
> - Ted
>
Thank you very much! 😉
--
With Best Regards,
Baokun Li
.
prev parent reply other threads:[~2022-12-01 6:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 13:26 [PATCH 0/2] ext4: fix a infinite loop in do_writepages after online resizing Baokun Li
2022-08-17 13:27 ` [PATCH 1/2] ext4: fix GDT corruption after online resizing with bigalloc enable and blocksize is 1024 Baokun Li
2022-08-17 13:27 ` [PATCH 2/2] ext4: add inode table check in __ext4_get_inode_loc to aovid possible infinite loop Baokun Li
2022-08-17 14:31 ` Jan Kara
2022-08-18 1:54 ` Baokun Li
2022-08-18 14:43 ` Ritesh Harjani (IBM)
2022-08-18 17:23 ` Jan Kara
2022-08-18 23:15 ` Ritesh Harjani (IBM)
2022-08-19 8:44 ` Jan Kara
2022-11-28 20:44 ` Theodore Ts'o
2022-11-29 8:54 ` Ritesh Harjani (IBM)
2022-11-29 21:12 ` [PATCH 0/2] ext4: fix a infinite loop in do_writepages after online resizing Theodore Ts'o
2022-11-30 2:08 ` Baokun Li
2022-12-01 3:42 ` Theodore Ts'o
2022-12-01 6:26 ` Baokun Li [this message]
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=faff95ef-7a4c-8176-4dac-aa1fb36d2bad@huawei.com \
--to=libaokun1@huawei.com \
--cc=adilger.kernel@dilger.ca \
--cc=enwlinux@gmail.com \
--cc=jack@suse.cz \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ritesh.list@gmail.com \
--cc=tytso@mit.edu \
--cc=yebin10@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai3@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