From: Tanmay Shah <tanmay.shah@amd.com>
To: Michal Simek <michal.simek@amd.com>,
Uros Bizjak <ubizjak@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: stable@vger.kernel.org, Jassi Brar <jassisinghbrar@gmail.com>
Subject: Re: [PATCH v2] mailbox: zynqmp: Remove invalid __percpu annotation in zynqmp_ipi_probe()
Date: Mon, 16 Dec 2024 11:47:33 -0600 [thread overview]
Message-ID: <65a1d19e-e793-4371-a33d-e2374908d7f8@amd.com> (raw)
In-Reply-To: <25eb1e35-83b0-46f4-9a9c-138c89665e05@amd.com>
Reviewed-by: Tanmay Shah <tanmay.shah@amd.com>
On 12/16/24 1:16 AM, Michal Simek wrote:
>
>
> On 12/14/24 10:12, Uros Bizjak wrote:
>> struct zynqmp_ipi_pdata __percpu *pdata is not a per-cpu variable,
>> so it should not be annotated with __percpu annotation.
>>
>> Remove invalid __percpu annotation to fix several
>>
>> zynqmp-ipi-mailbox.c:920:15: warning: incorrect type in assignment
>> (different address spaces)
>> zynqmp-ipi-mailbox.c:920:15: expected struct zynqmp_ipi_pdata
>> [noderef] __percpu *pdata
>> zynqmp-ipi-mailbox.c:920:15: got void *
>> zynqmp-ipi-mailbox.c:927:56: warning: incorrect type in argument 3
>> (different address spaces)
>> zynqmp-ipi-mailbox.c:927:56: expected unsigned int [usertype]
>> *out_value
>> zynqmp-ipi-mailbox.c:927:56: got unsigned int [noderef] __percpu *
>> ...
>>
>> and several
>>
>> drivers/mailbox/zynqmp-ipi-mailbox.c:924:9: warning: dereference of
>> noderef expression
>> ...
>>
>> sparse warnings.
>>
>> There were no changes in the resulting object file.
>>
>> Cc: stable@vger.kernel.org
>> Fixes: 6ffb1635341b ("mailbox: zynqmp: handle SGI for shared IPI")
>> Signed-off-by: Uros Bizjak <ubizjak@gmail.com>
>> Cc: Jassi Brar <jassisinghbrar@gmail.com>
>> Cc: Michal Simek <michal.simek@amd.com>
>> Cc: Tanmay Shah <tanmay.shah@amd.com>
>> ---
>> v2: - Fix typo in commit message
>> - Add Fixes and Cc: stable.
>> ---
>> drivers/mailbox/zynqmp-ipi-mailbox.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/mailbox/zynqmp-ipi-mailbox.c b/drivers/mailbox/
>> zynqmp-ipi-mailbox.c
>> index aa5249da59b2..0c143beaafda 100644
>> --- a/drivers/mailbox/zynqmp-ipi-mailbox.c
>> +++ b/drivers/mailbox/zynqmp-ipi-mailbox.c
>> @@ -905,7 +905,7 @@ static int zynqmp_ipi_probe(struct platform_device
>> *pdev)
>> {
>> struct device *dev = &pdev->dev;
>> struct device_node *nc, *np = pdev->dev.of_node;
>> - struct zynqmp_ipi_pdata __percpu *pdata;
>> + struct zynqmp_ipi_pdata *pdata;
>> struct of_phandle_args out_irq;
>> struct zynqmp_ipi_mbox *mbox;
>> int num_mboxes, ret = -EINVAL;
>
> Tanmay: Please take a look
>
> I think this patch is correct. Pdata structure is allocated only once
> not for every CPU and marking here is not correct. Information from
> zynqmp_ipi_pdata are likely fixed and the same for every CPU. Only IRQ
> handling is done per cpu basis but that's it.
>
> Reviewed-by: Michal Simek <michal.simek@amd.com>
>
> Thanks,
> Michal
>
next prev parent reply other threads:[~2024-12-16 17:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-14 9:12 [PATCH v2] mailbox: zynqmp: Remove invalid __percpu annotation in zynqmp_ipi_probe() Uros Bizjak
2024-12-16 7:16 ` Michal Simek
2024-12-16 17:47 ` Tanmay Shah [this message]
2025-01-16 8:52 ` Uros Bizjak
2025-01-16 16:07 ` Tanmay Shah
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=65a1d19e-e793-4371-a33d-e2374908d7f8@amd.com \
--to=tanmay.shah@amd.com \
--cc=jassisinghbrar@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=stable@vger.kernel.org \
--cc=ubizjak@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;
as well as URLs for NNTP newsgroup(s).