From: patchwork-bot+netdevbpf@kernel.org
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, robimarko@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, lkp@intel.com
Subject: Re: [net-next PATCH v3] net: phy: aquantia: drop wrong endianness conversion for addr and CRC
Date: Thu, 30 Nov 2023 04:10:30 +0000 [thread overview]
Message-ID: <170131743070.26382.14989467541066978129.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231128135928.9841-1-ansuelsmth@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 28 Nov 2023 14:59:28 +0100 you wrote:
> On further testing on BE target with kernel test robot, it was notice
> that the endianness conversion for addr and CRC in fw_load_memory was
> wrong.
>
> Drop the cpu_to_le32 conversion for addr load as it's not needed.
>
> Use get_unaligned_le32 instead of get_unaligned for FW data word load to
> correctly convert data in the correct order to follow system endian.
>
> [...]
Here is the summary with links:
- [net-next,v3] net: phy: aquantia: drop wrong endianness conversion for addr and CRC
https://git.kernel.org/netdev/net-next/c/7edce370d87a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-11-30 4:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 13:59 [net-next PATCH v3] net: phy: aquantia: drop wrong endianness conversion for addr and CRC Christian Marangi
2023-11-30 4:10 ` patchwork-bot+netdevbpf [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=170131743070.26382.14989467541066978129.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robimarko@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