From: Mike Rapoport <rppt@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Matthew Wilcox <willy@infradead.org>,
Mike Rapoport <rppt@kernel.org>,
Mike Rapoport <rppt@linux.ibm.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] include/linux/mm.h: remove duplicated declaration of page_mapping()
Date: Mon, 5 Apr 2021 18:13:55 +0300 [thread overview]
Message-ID: <20210405151355.9867-3-rppt@kernel.org> (raw)
In-Reply-To: <20210405151355.9867-1-rppt@kernel.org>
From: Mike Rapoport <rppt@linux.ibm.com>
There are two declarations of page_mapping() in include/linux/mm.h a dozen
lines apart.
Remove the older one with unnecessary "extern".
Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
---
include/linux/mm.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/include/linux/mm.h b/include/linux/mm.h
index 74a05dbdcc19..d831ca0fcfa1 100644
--- a/include/linux/mm.h
+++ b/include/linux/mm.h
@@ -1619,8 +1619,6 @@ void page_address_init(void);
#define page_address_init() do { } while(0)
#endif
-extern struct address_space *page_mapping(struct page *page);
-
extern struct address_space *__page_file_mapping(struct page *);
static inline
--
2.28.0
next prev parent reply other threads:[~2021-04-05 15:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 15:13 [PATCH 0/2] minor cleanups of include/linux/mm.h Mike Rapoport
2021-04-05 15:13 ` [PATCH 1/2] mm: move page_rmapping() and page_anon_vma() to mm/internal.h Mike Rapoport
2021-04-05 18:18 ` Matthew Wilcox
2021-04-05 20:00 ` kernel test robot
2021-04-05 15:13 ` Mike Rapoport [this message]
2021-04-05 18:16 ` [PATCH 2/2] include/linux/mm.h: remove duplicated declaration of page_mapping() Matthew Wilcox
2021-04-05 18:50 ` [PATCH 0/2] minor cleanups of include/linux/mm.h Matthew Wilcox
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=20210405151355.9867-3-rppt@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@linux.ibm.com \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).