From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Andrew Morton <akpm@linux-foundation.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
Minchan Kim <minchan@kernel.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH 0/2] zram: lockmap tweaks
Date: Fri, 24 Jul 2026 12:31:15 +0900 [thread overview]
Message-ID: <amLbxpYGMbqMI3fU@google.com> (raw)
In-Reply-To: <20260714141300.3945672-1-bigeasy@linutronix.de>
On (26/07/14 16:12), Sebastian Andrzej Siewior wrote:
> Sergey, this should be a follow up on
> https://lore.kernel.org/all/akza1qtgHm7zbjMW@google.com/
>
> Could you try if this does what I claimed it does?
>
> Sebastian Andrzej Siewior (2):
> zram: Move lockmap to be per-zram instead per table
> zram: Use a custom key for each zram object.
Seems that Sebastian is out-of-office (until Aug 13).
Andrew, can you please pick up these patches? Patch 2 has a minor
commit message "issue" - missing word "swap". As for unique name
for lockdep map comment - I will send a followup patch once this
series is in your tree.
Reviewed-by: Sergey Senozhatsky <senozhatsky@chromium.org>
Tested-by: Sergey Senozhatsky <senozhatsky@chromium.org>
prev parent reply other threads:[~2026-07-24 3:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 14:12 [PATCH 0/2] zram: lockmap tweaks Sebastian Andrzej Siewior
2026-07-14 14:12 ` [PATCH 1/2] zram: Move lockmap to be per-zram instead per table Sebastian Andrzej Siewior
2026-07-24 3:25 ` Sergey Senozhatsky
2026-07-14 14:13 ` [PATCH 2/2] zram: Use a custom key for each zram object Sebastian Andrzej Siewior
2026-07-24 3:24 ` Sergey Senozhatsky
2026-07-24 7:52 ` Sergey Senozhatsky
2026-07-24 3:26 ` [PATCH 0/2] zram: lockmap tweaks Sergey Senozhatsky
2026-07-24 3:31 ` Sergey Senozhatsky [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=amLbxpYGMbqMI3fU@google.com \
--to=senozhatsky@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=bigeasy@linutronix.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@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