From: Min-Hua Chen <minhuadotchen@gmail.com>
To: simon.horman@corigine.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
Subject: Re: [PATCH] net: stmmac: use le32_to_cpu for p->des0 and p->des1
Date: Fri, 19 May 2023 18:53:38 +0800 [thread overview]
Message-ID: <20230519105338.4793-1-minhuadotchen@gmail.com> (raw)
In-Reply-To: <ZGcs1sdy0RTrwNby@corigine.com>
Hi Simon,
>>
>> if (likely(desc_valid && ts_valid)) {
>> - if ((p->des0 == 0xffffffff) && (p->des1 == 0xffffffff))
>> + if ((le32_to_cpu(p->des0) == 0xffffffff) &&
>> + (le32_to_cpu(p->des1) == 0xffffffff))
>
>Hi Min-Hua Chen,
>
>I'm not sure if it makes a meaningful difference in practice - and
>certainly it won't on LE systems. But I wonder if it's nicer to do the
>conversion on the constant rather than the variable part of the comparison.
>
> if ((p->des0 == cpu_to_le32(0xffffffff)) &&
> (p->des1 == cpu_to_le32(0xffffffff)))
After reading your suggestion, I think:
the 'p->des0 == cpu_to_le32(0xffffffff)' gives the readers a hint that
p->des0 is __le32 type and I think it is easier (for me) to understand
than 'le32_to_cpu(p->des0) == 0xffffffff'
I will submit v2 for this, thanks for your comment.
thanks,
Min-Hua
prev parent reply other threads:[~2023-05-19 10:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 0:25 [PATCH] net: stmmac: use le32_to_cpu for p->des0 and p->des1 Min-Hua Chen
2023-05-19 8:01 ` Simon Horman
2023-05-19 10:53 ` 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=20230519105338.4793-1-minhuadotchen@gmail.com \
--to=minhuadotchen@gmail.com \
--cc=alexandre.torgue@foss.st.com \
--cc=davem@davemloft.net \
--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;
as well as URLs for NNTP newsgroup(s).