From: "Matthew Wilcox (Oracle)" <willy@infradead.org>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>
Subject: [PATCH 0/2] A small folio API enhancement for 5.17
Date: Thu, 13 Jan 2022 22:08:14 +0000 [thread overview]
Message-ID: <20220113220816.1257657-1-willy@infradead.org> (raw)
It turns out I want to use folio_put_refs() in two completely different
places (which would likely be in separate pull requests) for 5.18, and
there's a useful place to use it in 5.17, so I'm planning on sending
Linus a pull request for this pair of patches next week. The reviews
on patch 1 come from the folio GUP reviews over the last week, but I
doubt I've shown patch 2 to anybody before.
Matthew Wilcox (Oracle) (2):
mm: Add folio_put_refs()
filemap: Use folio_put_refs() in filemap_free_folio()
include/linux/mm.h | 20 ++++++++++++++++++++
mm/filemap.c | 10 ++++------
2 files changed, 24 insertions(+), 6 deletions(-)
--
2.33.0
next reply other threads:[~2022-01-13 22:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 22:08 Matthew Wilcox (Oracle) [this message]
2022-01-13 22:08 ` [PATCH 1/2] mm: Add folio_put_refs() Matthew Wilcox (Oracle)
2022-01-13 22:08 ` [PATCH 2/2] filemap: Use folio_put_refs() in filemap_free_folio() Matthew Wilcox (Oracle)
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=20220113220816.1257657-1-willy@infradead.org \
--to=willy@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).