From: Jakub Kicinski <kuba@kernel.org>
To: Jamal Hadi Salim <hadi@mojatatu.com>
Cc: Jamal Hadi Salim <jhs@mojatatu.com>,
netdev@vger.kernel.org, Jiri Pirko <jiri@resnulli.us>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Victor Nogueira <victor@mojatatu.com>,
stable@vger.kernel.org, Sashiko <sashiko-bot@kernel.org>,
hybris <hybris@mojatatu.ai>
Subject: Re: [PATCH net] net/sched: cls_api: reclaim an empty proto on the error path
Date: Mon, 28 Sep 2026 17:47:38 -0700 [thread overview]
Message-ID: <20260928174738.139f1365@kernel.org> (raw)
In-Reply-To: <CAAFAkD80zx12Cskdf8NaF1pkSbLUiYSeTEmvpSR8o6P2d-JEOg@mail.gmail.com>
On Sat, 26 Sep 2026 05:49:57 -0400 Jamal Hadi Salim wrote:
> On Fri, Sep 25, 2026 at 8:18 PM 'Jakub Kicinski' via Hyper-Yielding
> Back-end Review & Insight System <hybris@mojatatu.com> wrote:
> >
> > On Thu, 24 Sep 2026 04:32:49 -0400 Jamal Hadi Salim wrote:
> > > Tested-by: hybris <hybris@mojatatu.ai>
> >
> > Please stop adding these tags, they tell us absolutely nothing.
>
> This says that our _automated_ bot tested and it adds the tag before
> we send the patch.
> It does more than tdc for a specific patch set (e.g., PoCs for code
> paths not reachable via tdc) and it does find issues sometimes before
> we send out.
My main point is what I said - it tells us nothing upstream.
It's like a gerrit change-id tag, internal to mojatatu.
> If a human had done the same, wouldn't the protocol be for us to add this tag?
LLM != human.
next prev parent reply other threads:[~2026-09-29 0:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 8:32 [PATCH net] net/sched: cls_api: reclaim an empty proto on the error path Jamal Hadi Salim
2026-09-25 13:13 ` Simon Horman
2026-09-26 0:18 ` Jakub Kicinski
2026-09-26 9:49 ` Jamal Hadi Salim
2026-09-29 0:47 ` Jakub Kicinski [this message]
2026-09-29 8:42 ` Jamal Hadi Salim
2026-09-26 0:30 ` 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=20260928174738.139f1365@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hadi@mojatatu.com \
--cc=horms@kernel.org \
--cc=hybris@mojatatu.ai \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sashiko-bot@kernel.org \
--cc=stable@vger.kernel.org \
--cc=victor@mojatatu.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.