From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Breno Leitao <leitao@debian.org>,
Madalin Bucur <madalin.bucur@nxp.com>,
Ioana Ciornei <ioana.ciornei@nxp.com>,
Radu Bulie <radu-andrei.bulie@nxp.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Sean Anderson <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 2/3] net: dpaa_eth: add assertions about SGT entry offsets in sg_fd_to_skb()
Date: Wed, 30 Oct 2024 16:27:44 +0200 [thread overview]
Message-ID: <20241030142744.lt4vhiayg5gvnbuw@skbuf> (raw)
In-Reply-To: <20241029164317.50182-3-vladimir.oltean@nxp.com>
On Tue, Oct 29, 2024 at 06:43:16PM +0200, Vladimir Oltean wrote:
> Tested on LS1046A.
..and now also tested on T2080 (PowerPC), no apparent regressions.
next prev parent reply other threads:[~2024-10-30 14:29 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 [this message]
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
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=20241030142744.lt4vhiayg5gvnbuw@skbuf \
--to=vladimir.oltean@nxp.com \
--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 \
/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