mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: xiaolei wang <xiaolei.wang@windriver.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>, robh@kernel.org
Cc: linuxppc-dev@lists.ozlabs.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] soc: fsl: qbman: Remove redundant warnings
Date: Fri, 23 Aug 2024 07:39:28 +0800	[thread overview]
Message-ID: <4e7d4ed7-049b-47d7-8502-7f9d0bd9c196@windriver.com> (raw)
In-Reply-To: <3241a692-088d-4316-85c9-f2939a9179b2@csgroup.eu>


On 8/23/24 00:55, Christophe Leroy wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender 
> and know the content is safe.
>
> Hi,
>
> Le 02/08/2024 à 04:16, Xiaolei Wang a écrit :
>> [Vous ne recevez pas souvent de courriers de 
>> xiaolei.wang@windriver.com. Découvrez pourquoi ceci est important à 
>> https://aka.ms/LearnAboutSenderIdentification ]
>>
>> RESERVEDMEM_OF_DECLARE usage has been removed. For
>> non-popwerpc platforms, such as ls1043, this warning
>> is redundant. ls1043 itself uses shared-dma-mem.
>
> Can you please explain in more details ? I don't understand what it is
> redundant with.

commit 07f86917a450 used shared-dma-pool for QMan private memory 
allocations and

added this warning, but this is only for non-PPC platforms and using non 
shared-dma-mem

reservations. However, for non-PPC platforms, commit 3e62273ac63a will 
output a warning anyway.


At the same time, ls1043 already uses shared-dma-mem, so is this warning 
still necessary?


thanks

xiaolei

>
> Thanks
> Christophe
>
>>
>> Fixes: 3e62273ac63a ("soc: fsl: qbman: Remove RESERVEDMEM_OF_DECLARE 
>> usage")
>> Signed-off-by: Xiaolei Wang <xiaolei.wang@windriver.com>
>> ---
>>   drivers/soc/fsl/qbman/qman_ccsr.c | 2 --
>>   1 file changed, 2 deletions(-)
>>
>> diff --git a/drivers/soc/fsl/qbman/qman_ccsr.c 
>> b/drivers/soc/fsl/qbman/qman_ccsr.c
>> index 392e54f14dbe..aa5348f4902f 100644
>> --- a/drivers/soc/fsl/qbman/qman_ccsr.c
>> +++ b/drivers/soc/fsl/qbman/qman_ccsr.c
>> @@ -791,8 +791,6 @@ static int fsl_qman_probe(struct platform_device 
>> *pdev)
>>           * FQD memory MUST be zero'd by software
>>           */
>>          zero_priv_mem(fqd_a, fqd_sz);
>> -#else
>> -       WARN(1, "Unexpected architecture using non shared-dma-mem 
>> reservations");
>>   #endif
>>          dev_dbg(dev, "Allocated FQD 0x%llx 0x%zx\n", fqd_a, fqd_sz);
>>
>> -- 
>> 2.25.1
>>

  reply	other threads:[~2024-08-22 23:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-02  2:16 Xiaolei Wang
2024-08-22 16:55 ` Christophe Leroy
2024-08-22 23:39   ` xiaolei wang [this message]
2024-09-03  8:45 ` Christophe Leroy

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=4e7d4ed7-049b-47d7-8502-7f9d0bd9c196@windriver.com \
    --to=xiaolei.wang@windriver.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=robh@kernel.org \
    /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®