On Wed, 17 Jun 2026 17:52:24 -0400 Sasha Levin wrote:

On Wed, Jun 17, 2026 at 01:27:04PM -0700, Jakub Kicinski wrote:

quoted

On Wed, 17 Jun 2026 14:04:10 -0400 Sasha Levin wrote:  

quoted

Subject: [PATCH 6.6.y] rxrpc: Fix the ACK parser to extract the SACK table for parsing
Date: Wed, 17 Jun 2026 14:04:10 -0400
X-Mailer: git-send-email 2.53.0

From: David Howells <dhowells@redhat.com>

[ Upstream commit 333b6d5bb9f87827ac2639c737bf9613dbae7253 ]  

nit: you missed the "skip patchwork" header on this?  

Hey Jakub,

This one is a backport crafted in response to a failed backport of a stable
tagged commit.

I followed Greg's template to sending those backports to him, but I also think
that I do want folks to review the actual backport itself.

I see!
 

Do you think it makes sense to add a skip patchwork header on these too?

Hm, maybe some clever patchwork DB query would tell us what others do.
For networking the patchwork queue is purely for patches we have to
apply. So my preference would be to skip, but I didn't realize this
was intentional. 

It'd still be useful to add _some_ header that we could filter on. 
We have bots which complain if people repost patches too fast,
they will get confused.