From: patchwork-bot+netdevbpf@kernel.org
To: <edward.cree@amd.com>
Cc: linux-net-drivers@amd.com, davem@davemloft.net, kuba@kernel.org,
edumazet@google.com, pabeni@redhat.com, ecree.xilinx@gmail.com,
netdev@vger.kernel.org, habetsm.xilinx@gmail.com, arnd@arndb.de
Subject: Re: [PATCH v2 net-next 0/3] sfc: fix unaligned access in loopback selftests
Date: Mon, 26 Jun 2023 09:50:20 +0000 [thread overview]
Message-ID: <168777302005.21547.14985682307785128659.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1687545312.git.ecree.xilinx@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 23 Jun 2023 19:38:03 +0100 you wrote:
> From: Edward Cree <ecree.xilinx@gmail.com>
>
> Arnd reported that the sfc drivers each define a packed loopback_payload
> structure with an ethernet header followed by an IP header, whereas the
> kernel definition of iphdr specifies that this is 4-byte aligned,
> causing a W=1 warning.
> Fix this in each case by adding two bytes of leading padding to the
> struct, taking care that these are not sent on the wire.
> Tested on EF10; build-tested on Siena and Falcon.
>
> [...]
Here is the summary with links:
- [v2,net-next,1/3] sfc: use padding to fix alignment in loopback test
https://git.kernel.org/netdev/net-next/c/cf60ed469629
- [v2,net-next,2/3] sfc: siena: use padding to fix alignment in loopback test
https://git.kernel.org/netdev/net-next/c/30c24dd87f3f
- [v2,net-next,3/3] sfc: falcon: use padding to fix alignment in loopback test
https://git.kernel.org/netdev/net-next/c/1186c6b31ee1
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-06-26 9:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 18:38 [PATCH v2 net-next 0/3] sfc: fix unaligned access in loopback selftests edward.cree
2023-06-23 18:38 ` [PATCH v2 net-next 1/3] sfc: use padding to fix alignment in loopback test edward.cree
2023-08-12 8:23 ` Arnd Bergmann
2023-08-14 10:06 ` Edward Cree
2023-08-14 13:45 ` Arnd Bergmann
2023-08-14 15:56 ` Edward Cree
2023-06-23 18:38 ` [PATCH v2 net-next 2/3] sfc: siena: " edward.cree
2023-06-23 18:38 ` [PATCH v2 net-next 3/3] sfc: falcon: " edward.cree
2023-06-26 9:50 ` 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=168777302005.21547.14985682307785128659.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=edward.cree@amd.com \
--cc=habetsm.xilinx@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-net-drivers@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.