From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, leitao@debian.org,
madalin.bucur@nxp.com, ioana.ciornei@nxp.com,
radu-andrei.bulie@nxp.com, christophe.leroy@csgroup.eu,
sean.anderson@linux.dev, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH net-next 0/3] Fix sparse warnings in dpaa_eth driver
Date: Tue, 05 Nov 2024 03:10:29 +0000 [thread overview]
Message-ID: <173077622975.100940.17453964424124667340.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241029164317.50182-1-vladimir.oltean@nxp.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 29 Oct 2024 18:43:14 +0200 you wrote:
> This is a follow-up of the discussion at:
> https://lore.kernel.org/oe-kbuild-all/20241028-sticky-refined-lionfish-b06c0c@leitao/
> where I said I would take care of the sparse warnings uncovered by
> Breno's COMPILE_TEST change for the dpaa_eth driver.
>
> There was one warning that I decided to treat as an actual bug:
> https://lore.kernel.org/netdev/20241029163105.44135-1-vladimir.oltean@nxp.com/
> and what remains here are those warnings which I consider harmless.
>
> [...]
Here is the summary with links:
- [net-next,1/3] soc: fsl_qbman: use be16_to_cpu() in qm_sg_entry_get_off()
https://git.kernel.org/netdev/net-next/c/a12fcef429e1
- [net-next,2/3] net: dpaa_eth: add assertions about SGT entry offsets in sg_fd_to_skb()
https://git.kernel.org/netdev/net-next/c/81f8ee2823f3
- [net-next,3/3] net: dpaa_eth: extract hash using __be32 pointer in rx_default_dqrr()
https://git.kernel.org/netdev/net-next/c/0a746cf8bb6d
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:[~2024-11-05 3:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 16:43 [PATCH net-next 0/3] Fix sparse warnings in dpaa_eth driver Vladimir Oltean
2024-10-29 16:43 ` [PATCH net-next 1/3] soc: fsl_qbman: use be16_to_cpu() in qm_sg_entry_get_off() Vladimir Oltean
2024-10-30 10:39 ` Breno Leitao
2024-11-04 14:33 ` Christophe Leroy
2024-10-29 16:43 ` [PATCH net-next 2/3] net: dpaa_eth: add assertions about SGT entry offsets in sg_fd_to_skb() Vladimir Oltean
2024-10-30 14:27 ` Vladimir Oltean
2024-11-04 14:34 ` Christophe Leroy
2024-10-29 16:43 ` [PATCH net-next 3/3] net: dpaa_eth: extract hash using __be32 pointer in rx_default_dqrr() Vladimir Oltean
2024-10-30 10:35 ` Breno Leitao
2024-11-04 14:35 ` Christophe Leroy
2024-10-30 13:39 ` [PATCH net-next 0/3] Fix sparse warnings in dpaa_eth driver Madalin Bucur (OSS)
2024-11-05 3: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=173077622975.100940.17453964424124667340.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ioana.ciornei@nxp.com \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madalin.bucur@nxp.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=radu-andrei.bulie@nxp.com \
--cc=sean.anderson@linux.dev \
--cc=vladimir.oltean@nxp.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).