From: "Matthew Wilcox (Oracle)" <willy@infradead.org>
To: linux-cifs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>
Subject: [PATCH 2/2] filemap: Remove lock_page_killable()
Date: Wed, 8 Feb 2023 14:56:11 +0000 [thread overview]
Message-ID: <20230208145611.307706-3-willy@infradead.org> (raw)
In-Reply-To: <20230208145611.307706-1-willy@infradead.org>
There are no more callers; remove this function before any more appear.
Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
---
include/linux/pagemap.h | 10 ----------
1 file changed, 10 deletions(-)
diff --git a/include/linux/pagemap.h b/include/linux/pagemap.h
index cf0677419981..51b75b89730e 100644
--- a/include/linux/pagemap.h
+++ b/include/linux/pagemap.h
@@ -993,16 +993,6 @@ static inline int folio_lock_killable(struct folio *folio)
return 0;
}
-/*
- * lock_page_killable is like lock_page but can be interrupted by fatal
- * signals. It returns 0 if it locked the page and -EINTR if it was
- * killed while waiting.
- */
-static inline int lock_page_killable(struct page *page)
-{
- return folio_lock_killable(page_folio(page));
-}
-
/*
* folio_lock_or_retry - Lock the folio, unless this would block and the
* caller indicated that it can handle a retry.
--
2.35.1
next prev parent reply other threads:[~2023-02-08 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 14:56 [PATCH 0/2] Remove lock_page_killable() Matthew Wilcox (Oracle)
2023-02-08 14:56 ` [PATCH 1/2] cifs: Use a folio in cifs_page_mkwrite() Matthew Wilcox (Oracle)
2023-02-08 14:56 ` Matthew Wilcox (Oracle) [this message]
2023-02-09 19:43 ` [PATCH 0/2] Remove lock_page_killable() Steve French
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=20230208145611.307706-3-willy@infradead.org \
--to=willy@infradead.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@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).