From: Logan Gunthorpe <logang@deltatee.com>
To: linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net
Cc: Logan Gunthorpe <logang@deltatee.com>,
Stephen Bates <sbates@raithlin.com>,
Jeff Dike <jdike@addtoit.com>,
Richard Weinberger <richard@nod.at>,
Al Viro <viro@ZenIV.linux.org.uk>
Subject: [PATCH v2] um: add dummy ioremap and iounmap functions
Date: Thu, 25 May 2017 09:42:35 -0600 [thread overview]
Message-ID: <1495726955-27497-1-git-send-email-logang@deltatee.com> (raw)
The user mode architecture does not provide ioremap or iounmap, and
because of this, the arch won't build when the functions are used in some
core libraries.
I have designs to use these functions in scatterlist.c where they'd
almost certainly never be called on the um architecture but it does need
to compile. Thus, if the function is ever hit it returns NULL.
Signed-off-by: Logan Gunthorpe <logang@deltatee.com>
Signed-off-by: Stephen Bates <sbates@raithlin.com>
Cc: Jeff Dike <jdike@addtoit.com>
Cc: Richard Weinberger <richard@nod.at>
Cc: Al Viro <viro@ZenIV.linux.org.uk>
---
Changes for v2:
* Per feedback from Al Viro, the ioremap function was changed to
fail if it ever actually gets used.
arch/um/include/asm/io.h | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
create mode 100644 arch/um/include/asm/io.h
diff --git a/arch/um/include/asm/io.h b/arch/um/include/asm/io.h
new file mode 100644
index 0000000..f734673
--- /dev/null
+++ b/arch/um/include/asm/io.h
@@ -0,0 +1,17 @@
+#ifndef _ASM_UM_IO_H
+#define _ASM_UM_IO_H
+
+#define ioremap ioremap
+static inline void __iomem *ioremap(phys_addr_t offset, size_t size)
+{
+ return NULL;
+}
+
+#define iounmap iounmap
+static inline void iounmap(void __iomem *addr)
+{
+}
+
+#include <asm-generic/io.h>
+
+#endif
--
2.1.4
next reply other threads:[~2017-05-25 15:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 15:42 Logan Gunthorpe [this message]
2017-05-25 15:48 ` [PATCH v2] um: add dummy ioremap and iounmap functions Richard Weinberger
2017-05-25 15:53 ` Logan Gunthorpe
2017-05-27 18:08 ` Geert Uytterhoeven
2017-05-27 18:15 ` Logan Gunthorpe
2017-06-08 18:53 ` Logan Gunthorpe
2017-06-08 19:17 ` Richard Weinberger
2017-06-21 21:25 ` Logan Gunthorpe
2017-06-21 21:30 ` Richard Weinberger
2017-06-21 21:31 ` Logan Gunthorpe
2017-06-21 21:36 ` Arnd Bergmann
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=1495726955-27497-1-git-send-email-logang@deltatee.com \
--to=logang@deltatee.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
--cc=sbates@raithlin.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=viro@ZenIV.linux.org.uk \
/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