From: Christoph Hellwig <hch@lst.de>
To: Michal Simek <monstr@monstr.eu>, Tony Luck <tony.luck@intel.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@lists.linux-m68k.org, linux-ia64@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 2/3] microblaze: remove ioremap_fullcache
Date: Fri, 30 Aug 2019 18:12:36 +0200 [thread overview]
Message-ID: <20190830161237.23033-3-hch@lst.de> (raw)
In-Reply-To: <20190830161237.23033-1-hch@lst.de>
No callers of this function.
Signed-off-by: Christoph Hellwig <hch@lst.de>
---
arch/microblaze/include/asm/io.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/microblaze/include/asm/io.h b/arch/microblaze/include/asm/io.h
index c7968139486f..86c95b2a1ce1 100644
--- a/arch/microblaze/include/asm/io.h
+++ b/arch/microblaze/include/asm/io.h
@@ -40,7 +40,6 @@ extern void iounmap(volatile void __iomem *addr);
extern void __iomem *ioremap(phys_addr_t address, unsigned long size);
#define ioremap_nocache(addr, size) ioremap((addr), (size))
-#define ioremap_fullcache(addr, size) ioremap((addr), (size))
#define ioremap_wc(addr, size) ioremap((addr), (size))
#define ioremap_wt(addr, size) ioremap((addr), (size))
--
2.20.1
next prev parent reply other threads:[~2019-08-30 16:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 16:12 ioremap cleanups Christoph Hellwig
2019-08-30 16:12 ` [PATCH 1/3] m68k: remove ioremap_fullcache Christoph Hellwig
2019-08-30 16:12 ` Christoph Hellwig [this message]
2019-09-02 14:19 ` [PATCH 2/3] microblaze: " Michal Simek
2019-08-30 16:12 ` [PATCH 3/3] ia64: rename ioremap_nocache to ioremap_uc Christoph Hellwig
2019-09-02 7:53 ` ioremap cleanups Geert Uytterhoeven
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=20190830161237.23033-3-hch@lst.de \
--to=hch@lst.de \
--cc=geert@linux-m68k.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=monstr@monstr.eu \
--cc=tony.luck@intel.com \
/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).