From: "Arnd Bergmann" <arnd@arndb.de>
To: "Huacai Chen" <chenhuacai@loongson.cn>,
"Huacai Chen" <chenhuacai@kernel.org>
Cc: loongarch@lists.linux.dev, "Yinbo Zhu" <zhuyinbo@loongson.cn>,
"Xuefeng Li" <lixuefeng@loongson.cn>, guoren <guoren@kernel.org>,
"WANG Xuerui" <kernel@xen0n.name>,
"Jiaxun Yang" <jiaxun.yang@flygoat.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
"kernel test robot" <lkp@intel.com>
Subject: Re: [PATCH] soc: loongson: loongson2_pm: Fix build warnings for 32BIT
Date: Tue, 20 Oct 2026 00:18:39 +0200 [thread overview]
Message-ID: <e9489def-3fd1-48c7-a042-98395a3d1589@app.fastmail.com> (raw)
In-Reply-To: <20261019144240.4035274-1-chenhuacai@loongson.cn>
On Mon, Oct 19, 2026, at 16:42, Huacai Chen wrote:
> Since loongson_sysconf.suspend_addr is unsigned long, use "unsigned
> long" instead of "u64" for casting, so as to avoid build warnings for
> 32BIT:
>
> drivers/soc/loongson/loongson2_pm.c: In function 'loongson2_pm_probe':
>>> drivers/soc/loongson/loongson2_pm.c:178:49: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
> 178 | loongson_sysconf.suspend_addr =
> (u64)phys_to_virt(suspend_addr);
> |
>
> Cc: stable@vger.kernel.org
> Fixes: 3d9aba6618d1 ("LoongArch: Adjust build infrastructure for
> 32BIT/64BIT")
> Closes:
> https://lore.kernel.org/oe-kbuild-all/202610190549.WM2PO3vO-lkp@intel.com/
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Huacai Chen <chenhuacai@loongson.cn>
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
Feel free to pick that up through the loongarch tree, or send it to
soc@linux.linux.dev if you prefer us to pick it up through the soc tree.
Arnd
prev parent reply other threads:[~2026-10-19 22:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 14:42 Huacai Chen
2026-10-19 22:18 ` Arnd Bergmann [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=e9489def-3fd1-48c7-a042-98395a3d1589@app.fastmail.com \
--to=arnd@arndb.de \
--cc=chenhuacai@kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=guoren@kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=lixuefeng@loongson.cn \
--cc=lkp@intel.com \
--cc=loongarch@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=zhuyinbo@loongson.cn \
/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®