All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Weiner <hannes@cmpxchg.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Yosry Ahmed <yosry.ahmed@linux.dev>,
	Andrew Morton <akpm@linux-foundation.org>,
	Nhat Pham <nphamcs@gmail.com>,
	Chengming Zhou <chengming.zhou@linux.dev>,
	Minchan Kim <minchan@kernel.org>,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH mm-unstable 3/5] mm: zpool: Remove object mapping APIs
Date: Thu, 6 Mar 2025 09:15:44 -0500	[thread overview]
Message-ID: <20250306141544.GA290530@cmpxchg.org> (raw)
In-Reply-To: <Z8j_Ct0hTwAnd2-w@gondor.apana.org.au>

On Thu, Mar 06, 2025 at 09:48:58AM +0800, Herbert Xu wrote:
> On Wed, Mar 05, 2025 at 06:11:31AM +0000, Yosry Ahmed wrote:
> > zpool_map_handle(), zpool_unmap_handle(), and zpool_can_sleep_mapped()
> > are no longer used. Remove them with the underlying driver callbacks.
> > 
> > Signed-off-by: Yosry Ahmed <yosry.ahmed@linux.dev>
> > ---
> >  include/linux/zpool.h | 30 ---------------------
> >  mm/zpool.c            | 61 -------------------------------------------
> >  mm/zsmalloc.c         | 27 -------------------
> >  3 files changed, 118 deletions(-)
> 
> This patch breaks zbud and z3fold because they haven't been converted
> to the new interface.

They're both scheduled for removal and already gone in the mm tree.


  parent reply	other threads:[~2025-03-06 14:16 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-05  6:11 [PATCH mm-unstable 0/5] Switch zswap to object read/write APIs Yosry Ahmed
2025-03-05  6:11 ` [PATCH mm-unstable 1/5] mm: zpool: Add interfaces for " Yosry Ahmed
2025-03-05  8:18   ` Sergey Senozhatsky
2025-03-05 14:43   ` Johannes Weiner
2025-03-05 17:32   ` Nhat Pham
2025-03-05  6:11 ` [PATCH mm-unstable 2/5] mm: zswap: Use object read/write APIs instead of object mapping APIs Yosry Ahmed
2025-03-05 14:48   ` Johannes Weiner
2025-03-05 17:35   ` Nhat Pham
2025-03-05  6:11 ` [PATCH mm-unstable 3/5] mm: zpool: Remove " Yosry Ahmed
2025-03-05  8:17   ` Sergey Senozhatsky
2025-03-05 14:49   ` Johannes Weiner
2025-03-05 17:37   ` Nhat Pham
2025-03-06  1:48   ` Herbert Xu
2025-03-06  4:19     ` Herbert Xu
2025-03-06 16:55       ` Yosry Ahmed
2025-03-07  2:38         ` Herbert Xu
2025-03-07  5:19           ` Sergey Senozhatsky
2025-03-06 14:15     ` Johannes Weiner [this message]
2025-03-05  6:11 ` [PATCH mm-unstable 4/5] mm: zsmalloc: Remove object mapping APIs and per-CPU map areas Yosry Ahmed
2025-03-05  8:16   ` Sergey Senozhatsky
2025-03-05 14:51   ` Johannes Weiner
2025-03-05 17:39   ` Nhat Pham
2025-03-05 18:57   ` Yosry Ahmed
2025-03-05  6:11 ` [PATCH mm-unstable 5/5] mm: zpool: Remove zpool_malloc_support_movable() Yosry Ahmed
2025-03-05  8:14   ` Sergey Senozhatsky
2025-03-05 14:53   ` Johannes Weiner
2025-03-05 17:05   ` Nhat Pham
2025-03-05  8:18 ` [PATCH mm-unstable 0/5] Switch zswap to object read/write APIs 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=20250306141544.GA290530@cmpxchg.org \
    --to=hannes@cmpxchg.org \
    --cc=akpm@linux-foundation.org \
    --cc=chengming.zhou@linux.dev \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan@kernel.org \
    --cc=nphamcs@gmail.com \
    --cc=peterz@infradead.org \
    --cc=senozhatsky@chromium.org \
    --cc=tglx@linutronix.de \
    --cc=yosry.ahmed@linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.