From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dominique Martinet <dominique.martinet@atmark-techno.com>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
Kairui Song <kasong@tencent.com>,
Desheng Wu <deshengwu@tencent.com>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.15 0/3] ZRAM not releasing backing device backport
Date: Sun, 12 Jan 2025 11:03:42 +0100 [thread overview]
Message-ID: <2025011201-scorebook-kebab-2288@gregkh> (raw)
In-Reply-To: <20250110075844.1173719-1-dominique.martinet@atmark-techno.com>
On Fri, Jan 10, 2025 at 04:58:41PM +0900, Dominique Martinet wrote:
> This is a resend of the patchset discussed here[1] for the 5.15 tree.
>
> [1] https://lore.kernel.org/r/2025011052-backpedal-coat-2fec@gregkh
>
> I've picked the "do not keep dangling zcomp pointer" patch from the
> linux-rc tree at the time, so kept Sasha's SOB and added mine on top
> -- please let me know if it wasn't appropriate.
It's tricky to know, I dropped it and took what was in Linus's tree as
Sasha didn't actually review this one.
All now queued up, thanks!
greg k-h
next prev parent reply other threads:[~2025-01-12 10:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 7:58 [PATCH 5.15 0/3] ZRAM not releasing backing device backport Dominique Martinet
2025-01-10 7:58 ` [PATCH 5.15 1/3] drivers/block/zram/zram_drv.c: do not keep dangling zcomp pointer after zram reset Dominique Martinet
2025-01-11 19:04 ` Sasha Levin
2025-01-10 7:58 ` [PATCH 5.15 2/3] zram: check comp is non-NULL before calling comp_destroy Dominique Martinet
2025-01-10 22:59 ` kernel test robot
2025-01-11 19:05 ` Sasha Levin
2025-01-10 7:58 ` [PATCH 5.15 3/3] zram: fix uninitialized ZRAM not releasing backing device Dominique Martinet
2025-01-11 19:04 ` Sasha Levin
2025-01-12 10:03 ` Greg Kroah-Hartman [this message]
2025-01-14 7:39 ` [PATCH 5.15 0/3] ZRAM not releasing backing device backport Dominique Martinet
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=2025011201-scorebook-kebab-2288@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=deshengwu@tencent.com \
--cc=dominique.martinet@atmark-techno.com \
--cc=kasong@tencent.com \
--cc=patches@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=senozhatsky@chromium.org \
--cc=stable@vger.kernel.org \
/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