From: kernel test robot <lkp@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 2063/10451] drivers/gpu/drm/sti/sti_mixer.c:145:47: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Fri, 5 Jul 2024 23:07:04 +0800 [thread overview]
Message-ID: <202407052221.F4GPZtM2-lkp@intel.com> (raw)
Hi Ville,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 0b58e108042b0ed28a71cd7edf5175999955b233
commit: 74bde7581df3e18061119e1b27b63d0a9ea57b7a [2063/10451] drm/sti: Allow build with COMPILE_TEST=y
config: sh-randconfig-r133-20240705 (https://download.01.org/0day-ci/archive/20240705/202407052221.F4GPZtM2-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20240705/202407052221.F4GPZtM2-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202407052221.F4GPZtM2-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/sti/sti_mixer.c:145:47: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void const volatile [noderef] __iomem *ptr @@ got void * @@
drivers/gpu/drm/sti/sti_mixer.c:145:47: sparse: expected void const volatile [noderef] __iomem *ptr
drivers/gpu/drm/sti/sti_mixer.c:145:47: sparse: got void *
drivers/gpu/drm/sti/sti_mixer.c:168:38: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected void *addr @@ got void [noderef] __iomem * @@
drivers/gpu/drm/sti/sti_mixer.c:168:38: sparse: expected void *addr
drivers/gpu/drm/sti/sti_mixer.c:168:38: sparse: got void [noderef] __iomem *
vim +145 drivers/gpu/drm/sti/sti_mixer.c
a5f81078a56c6a Vincent Abriou 2016-02-04 139
a5f81078a56c6a Vincent Abriou 2016-02-04 140 static void mixer_dbg_mxn(struct seq_file *s, void *addr)
a5f81078a56c6a Vincent Abriou 2016-02-04 141 {
a5f81078a56c6a Vincent Abriou 2016-02-04 142 int i;
a5f81078a56c6a Vincent Abriou 2016-02-04 143
a5f81078a56c6a Vincent Abriou 2016-02-04 144 for (i = 1; i < 8; i++)
a5f81078a56c6a Vincent Abriou 2016-02-04 @145 seq_printf(s, "-0x%08X", (int)readl(addr + i * 4));
a5f81078a56c6a Vincent Abriou 2016-02-04 146 }
a5f81078a56c6a Vincent Abriou 2016-02-04 147
:::::: The code at line 145 was first introduced by commit
:::::: a5f81078a56c6ab57b7db2402ac64c34338004c5 drm/sti: add debugfs entries for MIXER crtc
:::::: TO: Vincent Abriou <vincent.abriou@st.com>
:::::: CC: Vincent Abriou <vincent.abriou@st.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-07-05 15:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202407052221.F4GPZtM2-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ville.syrjala@linux.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