From: Paolo Abeni <pabeni@redhat.com>
To: netdev-bot+sashiko@kernel.org,
muhammad.nazim.amirul.nazle.asmade@altera.com
Cc: netdev@vger.kernel.org, maxime.chevallier@bootlin.com,
andrew+netdev@lunn.ch, kuba@kernel.org, edumazet@google.com,
davem@davemloft.net, alexandre.torgue@foss.st.com,
mcoquelin.stm32@gmail.com, linux-arm-kernel@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: stmmac: Setup TBS only if HW supports it
Date: Thu, 24 Sep 2026 10:44:22 +0200 [thread overview]
Message-ID: <77c78712-d320-4a79-89e0-cfe11a33842f@redhat.com> (raw)
In-Reply-To: <179004548784.2160803.5129187589966240478@kernel.org>
On 9/22/26 04:51, netdev-bot+sashiko@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 2 potential
> issue(s) to consider.
>
> Critical: 0 · High: 0 (1) · Medium: 2 (1) · Low: 0 (1)
>
> If you believe none of the issues are legitimate, please reply to each
> issue of Medium severity or higher and explain why the AI is wrong.
> If any of them are legitimate and you plan to respin, please let patchwork
> know by including "pw-bot: cr" as a separate line at the end of your reply
> (one such reply per series is enough).
>
> - [Medium] The patch is a bug fix (it prevents a descriptor-format
> mismatch where the Tx ring is laid out with the 32-byte `struct…
> - [Medium] The new gate in stmmac_setup_dma_desc() (stmmac_main.c:4128)
> only checks the chip-wide capability bit `priv->dma_cap.tbssel`; it…
I think this patch should stay on net-next with no fixes tag, but the other
reported issue looks worth to be addressed.
/P
prev parent reply other threads:[~2026-09-24 8:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 2:35 muhammad.nazim.amirul.nazle.asmade
2026-09-22 2:51 ` netdev-bot+sashiko
2026-09-24 8:44 ` Paolo Abeni [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=77c78712-d320-4a79-89e0-cfe11a33842f@redhat.com \
--to=pabeni@redhat.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=maxime.chevallier@bootlin.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=muhammad.nazim.amirul.nazle.asmade@altera.com \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
/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
all inboxes | Powered by JetHome®