From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Rosen Penev <rosenp@gmail.com>
Cc: linux-mips@vger.kernel.org, Lauri Kasanen <cand@gmx.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mips: n64: add __iomem for writel call
Date: Tue, 26 May 2026 16:53:56 +0200 [thread overview]
Message-ID: <ahW0BDXCpPseQ4Sx@alpha.franken.de> (raw)
In-Reply-To: <20260509035727.1016256-1-rosenp@gmail.com>
On Fri, May 08, 2026 at 08:57:27PM -0700, Rosen Penev wrote:
> sparse: incorrect type in argument 2 (different address spaces) @@
> expected void volatile [noderef] __iomem *mem @@
> got unsigned int [usertype] *
>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202105261445.AcvPd2EE-lkp@intel.com/
> Fixes: baec970aa5ba ("mips: Add N64 machine type")
> Signed-off-by: Rosen Penev <rosenp@gmail.com>
> ---
> arch/mips/n64/init.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
applied to mips-next
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2026-05-26 15:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-09 3:57 [PATCH] mips: n64: add __iomem for writel call Rosen Penev
2026-05-26 14:53 ` Thomas Bogendoerfer [this message]
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=ahW0BDXCpPseQ4Sx@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=cand@gmx.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=rosenp@gmail.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