From: Ruan Jinjie <ruanjinjie@huawei.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>,
"mpe@ellerman.id.au" <mpe@ellerman.id.au>,
"npiggin@gmail.com" <npiggin@gmail.com>,
"joel@jms.id.au" <joel@jms.id.au>,
"Julia.Lawall@inria.fr" <Julia.Lawall@inria.fr>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] powerpc/mpic_msgr: fix cast removes address space of expression warnings
Date: Fri, 30 Sep 2022 14:37:05 +0800 [thread overview]
Message-ID: <2afc52b8-3e4d-c61e-95ed-885520b95a17@huawei.com> (raw)
In-Reply-To: <4d3b7f83-498e-deb2-ce2a-c17d4b22a078@csgroup.eu>
On 2022/9/30 14:09, Christophe Leroy wrote:
>
>
> Le 01/09/2022 à 10:54, ruanjinjie a écrit :
>> [Vous ne recevez pas souvent de courriers de ruanjinjie@huawei.com. Découvrez pourquoi ceci est important à https://aka.ms/LearnAboutSenderIdentification ]
>>
>> When build Linux kernel, encounter the following warnings:
>>
>> ./arch/powerpc/sysdev/mpic_msgr.c:230:38: warning: cast removes address space '__iomem' of expression
>> ./arch/powerpc/sysdev/mpic_msgr.c:230:27: warning: incorrect type in assignment (different address spaces)
>>
>> The data type of msgr->mer and msgr->base are 'u32 __iomem *', but
>> converted to 'u32 *' and 'u8 *' directly and cause above warnings, now
>> recover their data types to fix these warnings.
>
> I think the best would be to change MPIC_MSGR_MER_OFFSET to 0x40 and
> then drop the casts completely:
>
> msgr->mer = msgr->base + MPIC_MSGR_MER_OFFSET;
>
I think this is good to solve the warning.
>>
>> Signed-off-by: ruanjinjie <ruanjinjie@huawei.com>
>> ---
>> arch/powerpc/sysdev/mpic_msgr.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/powerpc/sysdev/mpic_msgr.c b/arch/powerpc/sysdev/mpic_msgr.c
>> index 698fefaaa6dd..cbb0d24f15ba 100644
>> --- a/arch/powerpc/sysdev/mpic_msgr.c
>> +++ b/arch/powerpc/sysdev/mpic_msgr.c
>> @@ -227,7 +227,7 @@ static int mpic_msgr_probe(struct platform_device *dev)
>>
>> reg_number = block_number * MPIC_MSGR_REGISTERS_PER_BLOCK + i;
>> msgr->base = msgr_block_addr + i * MPIC_MSGR_STRIDE;
>> - msgr->mer = (u32 *)((u8 *)msgr->base + MPIC_MSGR_MER_OFFSET);
>> + msgr->mer = (u32 __iomem *)((u8 __iomem *)msgr->base + MPIC_MSGR_MER_OFFSET);
>> msgr->in_use = MSGR_FREE;
>> msgr->num = i;
>> raw_spin_lock_init(&msgr->lock);
>> --
>> 2.25.1
next prev parent reply other threads:[~2022-09-30 6:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 8:54 [PATCH -next] powerpc/mpic_msgr: fix cast removes address space of expression warnings ruanjinjie
2022-09-30 1:34 ` Ruan Jinjie
2022-09-30 6:09 ` Christophe Leroy
2022-09-30 6:37 ` Ruan Jinjie [this message]
2022-09-30 7:25 ` Michael Ellerman
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=2afc52b8-3e4d-c61e-95ed-885520b95a17@huawei.com \
--to=ruanjinjie@huawei.com \
--cc=Julia.Lawall@inria.fr \
--cc=christophe.leroy@csgroup.eu \
--cc=joel@jms.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@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