From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Qu Wenruo <wqu@suse.com>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
Minchan Kim <minchan@kernel.org>,
Brian Geffon <bgeffon@google.com>,
linux-block@vger.kernel.org, linux-mm@kvack.org,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v2] zram: do not forget to endio for partial discard requests
Date: Tue, 31 Mar 2026 16:43:50 +0900 [thread overview]
Message-ID: <act7DBWOwe42i38Z@google.com> (raw)
In-Reply-To: <c2a593e1-cbde-46bb-a32a-c9db38c62801@suse.com>
On (26/03/31 18:10), Qu Wenruo wrote:
> And forgot to mention, I'm just a messenger who also did the triage.
>
> The original reporter is Avinesh Kumar <avinesh.kumar@suse.com>, who noticed
> a test failure from LTP runs.
Cc-ed Avinesh on the v3.
next prev parent reply other threads:[~2026-03-31 7:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 7:35 [PATCH v2] zram: do not forget to endio for partial discard requests Sergey Senozhatsky
2026-03-31 7:40 ` Qu Wenruo
2026-03-31 7:43 ` Sergey Senozhatsky [this message]
2026-03-31 7:40 ` Sergey Senozhatsky
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=act7DBWOwe42i38Z@google.com \
--to=senozhatsky@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=bgeffon@google.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=wqu@suse.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