From: Paolo Abeni <pabeni@redhat.com>
To: Jamal Hadi Salim <jhs@mojatatu.com>, Jakub Kicinski <kuba@kernel.org>
Cc: Simon Horman <horms@kernel.org>,
Victor Nogueira <victor@mojatatu.com>,
Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: sashiko or lore confused?
Date: Mon, 12 Oct 2026 12:58:09 +0200 [thread overview]
Message-ID: <a3a68d65-9eca-41ee-a70a-0db8dbb0385c@redhat.com> (raw)
In-Reply-To: <CAM0EoMn6JoLVHdhX1GB1wBcw3fVZ42ePKXDqsWK-4STj87vEEQ@mail.gmail.com>
On 10/12/26 02:00, Jamal Hadi Salim wrote:
> Some threads seem stuck somewhere in the ether for sometime now. I
> asking because i have a backlog and dont want to flood things..
>
> 1) Sashiko nipa review is missing on the act_api duplicate-index series
> ========================================================================
> The nipa sashiko never produced a review for this series: gemini
> sahiko reviewed it ("No issues found").
>
> Original posting (v1, 2026-09-22):
> https://lore.kernel.org/netdev/QDISC-K1TH.v1.20260922072206@mojatatu.com/
> [PATCH net 1/2] net/sched: act_api: reject duplicate actions in a batch
We had a few PW outages recently, and that impacts directly clashiko. Also the
threading (new version in reply to the old one) tends to confuse PW.
> 2) What is still left on these two?
> ===================================
> (a) act_api_delete_duplicate_index_refcount_uaf (links above). After the
> 2/2 delivery glitch and the two reposts, is anything still
> outstanding from the maintainer side, or is this only waiting on the
> missing nipa review?
PW still did not handle the repost correctly. I think you need to send again the
patches, and please send them in a new thread!
> (b) teql_xmit_path_pre_existing_bugs -- series [PATCH net 0/2] QDISC-6HS9,
> sent 2026-09-29. Both Sashiko providers reviewed it: gemini "No
> issues found"; nipa one Medium (commit-message doc wording) plus a
> pre-existing, out-of-scope item (the consumed-skb UAF, tracked
> separately). We do not plan a respin for the doc wording. Is
> anything else outstanding before merge?
>
> cover: https://lore.kernel.org/netdev/QDISC-6HS9.v1.20260928064754@mojatatu.com/
> 1/2: https://lore.kernel.org/netdev/QDISC-6HS9.v1.20260928064754@mojatatu.com.1/
> 2/2: https://lore.kernel.org/netdev/QDISC-6HS9.v1.20260928064754@mojatatu.com.2/
>
I'm unsure who set the above to changes requested. Your reply looks legit.
I reset the series to 'new' status, but we have a long backlog, I'm unsure
I'll be able to process the above before PW will archive the post. In such
a case a repost would be needed :(
/P
next prev parent reply other threads:[~2026-10-12 10:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 0:00 sashiko or lore confused? Jamal Hadi Salim
2026-10-12 10:58 ` Paolo Abeni [this message]
2026-10-12 11:48 ` Jamal Hadi Salim
2026-10-12 13:37 ` Paolo Abeni
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=a3a68d65-9eca-41ee-a70a-0db8dbb0385c@redhat.com \
--to=pabeni@redhat.com \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=kuba@kernel.org \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox