mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: tony.luck@intel.com
Cc: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
	fengguang.wu@intel.com, mingo@kernel.org, bp@suse.de,
	"Luis R. Rodriguez" <mcgrof@kernel.org>
Subject: [PATCH] ia64: define ioremap_uc()
Date: Mon,  7 Mar 2016 12:34:54 -0800	[thread overview]
Message-ID: <1457382894-13553-1-git-send-email-mcgrof@kernel.org> (raw)
In-Reply-To: <201603062005.lhOBibd1%fengguang.wu@intel.com>

All architectures now need ioremap_uc(), ia64 seems defines
this already through its ioremap_nocache() and it already
ensures it *only* uses UC.

Reported-by: 0 day bot
Signed-off-by: Luis R. Rodriguez <mcgrof@kernel.org>
---

Note, this is actually needed since v4.3 to complete an allyesconfig
compile on ia64, there were others archs that needed this, and this
one just seems to have fallen through the cracks.

 arch/ia64/include/asm/io.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/ia64/include/asm/io.h b/arch/ia64/include/asm/io.h
index a865d2a04f75..5de673ac9cb1 100644
--- a/arch/ia64/include/asm/io.h
+++ b/arch/ia64/include/asm/io.h
@@ -433,6 +433,7 @@ static inline void __iomem * ioremap_cache (unsigned long phys_addr, unsigned lo
 	return ioremap(phys_addr, size);
 }
 #define ioremap_cache ioremap_cache
+#define ioremap_uc ioremap_nocache
 
 
 /*
-- 
2.7.2

  parent reply	other threads:[~2016-03-07 20:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-06 12:14 drivers/video/fbdev/aty/atyfb_base.c:3461:2: error: implicit declaration of function 'ioremap_uc' kbuild test robot
2016-03-07 20:29 ` Luis R. Rodriguez
2016-03-07 20:34 ` Luis R. Rodriguez [this message]
2016-03-15 22:07   ` [PATCH] ia64: define ioremap_uc() Luis R. Rodriguez
2016-03-15 22:15     ` Luck, Tony
2016-03-15 22:13   ` Andrew Morton
2016-03-15 22:17     ` Luck, Tony

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=1457382894-13553-1-git-send-email-mcgrof@kernel.org \
    --to=mcgrof@kernel.org \
    --cc=bp@suse.de \
    --cc=fengguang.wu@intel.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --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

all inboxes | Powered by JetHome®