From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Chris Mason <clm@meta.com>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
Minchan Kim <minchan@kernel.org>,
Brian Geffon <bgeffon@google.com>,
David Stevens <stevensd@google.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-block@vger.kernel.org
Subject: Re: [PATCH 2/3] zram: rename internal slot API
Date: Thu, 15 Jan 2026 12:01:46 +0900 [thread overview]
Message-ID: <z6qsrmojsh5rcrlv2dggbjgyb5q5qmdgrafeq4zknpfwdrlaf6@zkcqyzrwpiro> (raw)
In-Reply-To: <20260114123658.1231407-1-clm@meta.com>
On (26/01/14 04:36), Chris Mason wrote:
> > +static void mark_slot_accessed(struct zram *zram, u32 index)
> > +{
> > + clear_slot_flag(zram, index, ZRAM_IDLE);
> > + clear_slot_flag(zram, index, ZRAM_PP_SLOT);
> > +#ifdef CONFIG_ZRAM_TRACK_ENTRY_ACTIME
> > + zram->table[index].attr.ac_time = ktime_get_boottime();
Hmm, this should have not happened. Thanks for catching this.
Let me take a look.
next prev parent reply other threads:[~2026-01-15 3:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 5:47 [PATCH 1/3] zram: use u32 for entry ac_time tracking Sergey Senozhatsky
2025-12-15 5:47 ` [PATCH 2/3] zram: rename internal slot API Sergey Senozhatsky
2026-01-14 12:36 ` Chris Mason
2026-01-15 3:01 ` Sergey Senozhatsky [this message]
2025-12-15 5:47 ` [PATCH 3/3] zram: trivial fix of recompress_slot() coding styles Sergey Senozhatsky
2025-12-15 22:31 ` [PATCH 1/3] zram: use u32 for entry ac_time tracking Brian Geffon
2025-12-16 0:59 ` Sergey Senozhatsky
2025-12-16 1:17 ` Brian Geffon
2026-01-14 12:45 ` Chris Mason
2026-01-15 3:13 ` 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=z6qsrmojsh5rcrlv2dggbjgyb5q5qmdgrafeq4zknpfwdrlaf6@zkcqyzrwpiro \
--to=senozhatsky@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=bgeffon@google.com \
--cc=clm@meta.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=stevensd@google.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