All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: netdev-bot+sashiko@kernel.org, nshettyj@marvell.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	naveenm@marvell.com, sgoutham@marvell.com, gakula@marvell.com,
	rkannoth@marvell.com, sbhatta@marvell.com, bbhushan2@marvell.com,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org
Subject: Re: [net-next,v2] octeontx2-pf: Add NIXLF error and poison interrupt handlers
Date: Thu, 3 Sep 2026 12:32:12 +0200	[thread overview]
Message-ID: <0d041c08-1deb-40c3-b05a-e4657844b3a4@redhat.com> (raw)
In-Reply-To: <178842771187.3394541.7325489363068011329@kernel.org>

On 9/3/26 11:28 AM, 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 · Medium: 1 · Low: 1
> 
> - [Medium] The patch bundles undisclosed VF-side changes that the commit
>   message (subject "octeontx2-pf: Add NIXLF error and poison interrupt…

IMHO this comment is borderline relevant, but addressing it requires a
level of effort that would offset the benefit, as this is only for code
archeology's sake and we already have the lore link in the changelog.

/P


  reply	other threads:[~2026-09-03 10:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31  6:26 [PATCH net-next v2] octeontx2-pf: Add NIXLF error and poison interrupt handlers nshettyj
2026-09-03  9:28 ` [net-next,v2] " netdev-bot+sashiko
2026-09-03 10:32   ` Paolo Abeni [this message]
2026-09-03 10:50 ` [PATCH net-next v2] " 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=0d041c08-1deb-40c3-b05a-e4657844b3a4@redhat.com \
    --to=pabeni@redhat.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=bbhushan2@marvell.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gakula@marvell.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=naveenm@marvell.com \
    --cc=netdev-bot+sashiko@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nshettyj@marvell.com \
    --cc=rkannoth@marvell.com \
    --cc=sbhatta@marvell.com \
    --cc=sgoutham@marvell.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.