From: Min-Hua Chen <minhuadotchen@gmail.com>
To: ecree.xilinx@gmail.com
Cc: alexandre.torgue@foss.st.com, davem@davemloft.net,
edumazet@google.com, joabreu@synopsys.com, kuba@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
mcoquelin.stm32@gmail.com, minhuadotchen@gmail.com,
netdev@vger.kernel.org, pabeni@redhat.com,
peppe.cavallaro@st.com, simon.horman@corigine.com
Subject: Re: [PATCH v3] net: stmmac: compare p->des0 and p->des1 with __le32 type values
Date: Mon, 22 May 2023 23:36:15 +0800 [thread overview]
Message-ID: <20230522153615.247577-1-minhuadotchen@gmail.com> (raw)
In-Reply-To: <9e6b813a-bc1a-6a39-904d-5c45f983cd23@gmail.com>
hi Edward,
>>> On Fri, 19 May 2023 19:50:28 +0800 Min-Hua Chen wrote:
>>>> - if ((p->des0 == 0xffffffff) && (p->des1 == 0xffffffff))
>>>> + if (p->des0 == cpu_to_le32(0xffffffff) &&
>>>> + p->des1 == cpu_to_le32(0xffffffff))
>>>
>>> Can you try to fix the sparse tool instead? I believe it already
>>> ignores such errors for the constant of 0, maybe it can be taught
>>> to ignore all "isomorphic" values?
>>>
>>
>> I downloaded the source code of sparse and I'm afraid that I cannot make
>> 0xFFFFFFFF ignored easily. I've tried ~0 instead of 0xFFFFFF,
>> but it did not work with current sparse.
>>
>> 0 is a special case mentioned in [1].
>
>I believe you can do something like
> if ((p->des0 == ~(__le32)0) && (p->des1 == ~(__le32)0))
> and sparse will accept that, because the cast is allowed under the
> special case.
>HTH,
>-ed
I tested ~(__le32)0 and it worked: sparse accpets this.
Thanks for sharing this.
cheers,
Min-Hua
prev parent reply other threads:[~2023-05-22 15:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 11:50 Min-Hua Chen
2023-05-19 13:17 ` Simon Horman
2023-05-19 22:27 ` Jakub Kicinski
2023-05-20 1:55 ` Min-Hua Chen
2023-05-20 4:04 ` Jakub Kicinski
2023-05-20 7:34 ` Min-Hua Chen
2023-05-22 14:09 ` Edward Cree
2023-05-22 15:36 ` Min-Hua Chen [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=20230522153615.247577-1-minhuadotchen@gmail.com \
--to=minhuadotchen@gmail.com \
--cc=alexandre.torgue@foss.st.com \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peppe.cavallaro@st.com \
--cc=simon.horman@corigine.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
all inboxes | Powered by JetHome®