From: Christoph Hellwig <hch@lst.de>
To: Usama Arif <usama.arif@linux.dev>
Cc: Christoph Hellwig <hch@lst.de>,
baoquan.he@linux.dev, akpm@linux-foundation.org,
chrisl@kernel.org, kasong@tencent.com, nphamcs@gmail.com,
shikemeng@huaweicloud.com, youngjun.park@lge.com,
ryncsn@gmail.com, trondmy@kernel.org, anna@kernel.org,
sfrench@samba.org, linux-mm@kvack.org,
linux-cifs@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 2/3] mm/swap: add a new swap_ops.h header to allow for pluggable swap ops
Date: Thu, 23 Jul 2026 07:27:06 +0200 [thread overview]
Message-ID: <20260723052706.GB7565@lst.de> (raw)
In-Reply-To: <20260722163218.1240273-1-usama.arif@linux.dev>
On Wed, Jul 22, 2026 at 09:32:17AM -0700, Usama Arif wrote:
> > +struct swap_io_ctx {
> > + struct swap_iocb *sio;
> > + struct swap_info_struct *sis;
> > +};
>
> zswap uses this struct, I think you need to include the header in zswap.c
> as well, good to check if the build is passing with CONFIG_ZSWAP=y
Yes. The buildbot was nice enough to remind me of that just a little
after it gave an all ok...
next prev parent reply other threads:[~2026-07-23 5:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 13:06 swap_ops updates Christoph Hellwig
2026-07-22 13:06 ` [PATCH 1/3] mm/swap: revert to single-folio writes for synchronous swap devices Christoph Hellwig
2026-07-22 16:36 ` Usama Arif
2026-07-23 5:25 ` Christoph Hellwig
2026-07-22 16:57 ` Chris Li
2026-07-23 17:59 ` Kairui Song
2026-07-22 13:06 ` [PATCH 2/3] mm/swap: add a new swap_ops.h header to allow for pluggable swap ops Christoph Hellwig
2026-07-22 16:32 ` Usama Arif
2026-07-23 5:27 ` Christoph Hellwig [this message]
2026-07-22 16:56 ` Chris Li
2026-07-22 13:06 ` [PATCH 3/3] mm/swap: move swap_ops into file systems for file system-based swap Christoph Hellwig
2026-07-22 17:07 ` Chris Li
-- strict thread matches above, loose matches on Subject: below --
2026-07-23 5:46 swap_ops updates v2 Christoph Hellwig
2026-07-23 5:46 ` [PATCH 2/3] mm/swap: add a new swap_ops.h header to allow for pluggable swap ops Christoph Hellwig
2026-07-23 17:11 ` Chris Li
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=20260723052706.GB7565@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=anna@kernel.org \
--cc=baoquan.he@linux.dev \
--cc=chrisl@kernel.org \
--cc=kasong@tencent.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=nphamcs@gmail.com \
--cc=ryncsn@gmail.com \
--cc=sfrench@samba.org \
--cc=shikemeng@huaweicloud.com \
--cc=trondmy@kernel.org \
--cc=usama.arif@linux.dev \
--cc=youngjun.park@lge.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