All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, Ira Weiny <ira.weiny@intel.com>,
	Christoph Hellwig <hch@lst.de>,
	linux-block@vger.kernel.org, ceph-devel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/5] Remove zero_user()
Date: Fri, 13 Jun 2025 07:24:32 +0200	[thread overview]
Message-ID: <20250613052432.GA8802@lst.de> (raw)
In-Reply-To: <20250612143443.2848197-1-willy@infradead.org>

On Thu, Jun 12, 2025 at 03:34:36PM +0100, Matthew Wilcox (Oracle) wrote:
> The zero_user() API is almost unused these days.  Finish the job of
> removing it.

Both the block layer users really should use bvec based helpers.
I was planning to get to that this merge window.  Can we queue up
just the other two removals for and remove zero_user after -rc1
to reduce conflicts?


  parent reply	other threads:[~2025-06-13  5:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-12 14:34 [PATCH 0/5] Remove zero_user() Matthew Wilcox (Oracle)
2025-06-12 14:34 ` [PATCH 1/5] bio: Use memzero_page() in bio_truncate() Matthew Wilcox (Oracle)
2025-06-25 10:40   ` Alex Markuze
2025-06-12 14:34 ` [PATCH 2/5] null_blk: Use memzero_page() Matthew Wilcox (Oracle)
2025-06-25 10:41   ` Alex Markuze
2025-06-12 14:34 ` [PATCH 3/5] direct-io: " Matthew Wilcox (Oracle)
2025-06-25 10:40   ` Alex Markuze
2025-06-12 14:34 ` [PATCH 4/5] ceph: Convert ceph_zero_partial_page() to use a folio Matthew Wilcox (Oracle)
2025-06-12 19:36   ` Viacheslav Dubeyko
2025-06-12 14:34 ` [PATCH 5/5] mm: Remove zero_user() Matthew Wilcox (Oracle)
2025-06-25 10:41   ` Alex Markuze
2025-06-13  5:24 ` Christoph Hellwig [this message]
2025-06-13 19:51   ` [PATCH 0/5] " Matthew Wilcox
2025-06-13 20:04     ` Andrew Morton

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=20250613052432.GA8802@lst.de \
    --to=hch@lst.de \
    --cc=akpm@linux-foundation.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=ira.weiny@intel.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=willy@infradead.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 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.