From: Simon Horman <horms@kernel.org>
To: Sudheer Kumar Doredla <s-doredla@ti.com>
Cc: s-vadapalli@ti.com, rogerq@kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, gnault@redhat.com, linux-omap@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
t-patil@ti.com, j-keerthy@ti.com
Subject: Re: [PATCH net]
Date: Wed, 8 Jan 2025 10:21:40 +0000 [thread overview]
Message-ID: <20250108102140.GI2772@kernel.org> (raw)
In-Reply-To: <20250108081303.228653-1-s-doredla@ti.com>
On Wed, Jan 08, 2025 at 01:43:03PM +0530, Sudheer Kumar Doredla wrote:
> cpsw_ale_get_field was returning incorrect data when requesting higher
> word fields. Additionally, cpsw_ale_set_field was writing incorrect
> data into the ALE entry while updating.
>
> For example, while reading word2, word3 fields (62 to 64 bits), the word3
> data was shifted to an incorrect position after reading. The same issue
> occurred when setting an ALE entry.
>
> This patch fixes the shifting of the word3 data by aligning it with the
> required fileds, ensuring the correct value is returned from
> cpsw_ale_get_field, even for higher words.
> It also ensures the correct vlaue is written into ALE entry using
> cpsw_ale_set_field.
Hi Sudheer,
It would be interesting to include some information on how this problem
manifests in practice.
And, as a fix for net this should have a fixes tag.
(Immediately above the other tags, no blank line in between.)
Perhaps this one is appropriate?
Fixes: b685f1a58956 ("net: ethernet: ti: cpsw_ale: Fix cpsw_ale_get_field()/cpsw_ale_set_field()")
> Signed-off-by: Sudheer Kumar Doredla <s-doredla@ti.com>
And, lastly, the subject for this patch seems to be missing.
Please add one:
Subject: [PATCH v2 net] net: ethernet: ti: cpsw_ale: ...
The code changes themselves look good to me.
So with the above addressed, feel free to include.
Reviewed-by: Simon Horman <horms@kernel.org>
...
--
pw-bot: changes-requested
prev parent reply other threads:[~2025-01-08 10:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 8:13 [PATCH net] Sudheer Kumar Doredla
2025-01-08 10:21 ` Simon Horman [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=20250108102140.GI2772@kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gnault@redhat.com \
--cc=j-keerthy@ti.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rogerq@kernel.org \
--cc=s-doredla@ti.com \
--cc=s-vadapalli@ti.com \
--cc=t-patil@ti.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).