From: David Sterba <dsterba@suse.cz>
To: Mikhail Zaslonko <zaslonko@linux.ibm.com>
Cc: Qu Wenruo <wqu@suse.com>,
linux-btrfs@vger.kernel.org, linux-s390@vger.kernel.org,
Heiko Carstens <hca@linux.ibm.com>
Subject: Re: [PATCH] btrfs: fix the folio leak on S390 hardware acceleration
Date: Fri, 6 Feb 2026 17:00:18 +0100 [thread overview]
Message-ID: <20260206160018.GY26902@twin.jikos.cz> (raw)
In-Reply-To: <4055f852-0488-4ccf-abb5-bc5f8d2c9635@linux.ibm.com>
On Thu, Feb 05, 2026 at 11:54:21PM +0100, Mikhail Zaslonko wrote:
> Hello Qu,
>
> Sorry for the late response.
> I ran some test on s390 including folio-leak verification. LGTM.
>
> Tested-by: Mikhail Zaslonko <zaslonko@linux.ibm.com>
Thanks for testing, the patch has been merged to 6.19.
next prev parent reply other threads:[~2026-02-06 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bcf36edfb7ac3caf3373174e741bb29c0feb268b.1768802004.git.wqu@suse.com>
2026-01-20 22:52 ` [PATCH] btrfs: fix the folio leak on S390 hardware acceleration Qu Wenruo
2026-01-21 9:28 ` Heiko Carstens
2026-02-05 22:54 ` Mikhail Zaslonko
2026-02-06 16:00 ` David Sterba [this message]
2026-01-21 4:05 ` David Sterba
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=20260206160018.GY26902@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=hca@linux.ibm.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=wqu@suse.com \
--cc=zaslonko@linux.ibm.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