From: Jakub Kicinski <kuba@kernel.org>
To: netdev@vger.kernel.org
Subject: [ANN] patchwork turbulence
Date: Tue, 8 Sep 2026 15:56:40 -0700 [thread overview]
Message-ID: <20260908155640.02d96800@kernel.org> (raw)
Hi!
JFYI the kernel.org admins upgraded patchwork, which broke a bunch of
things. One very visible issue is that a number of patches go marked
as conflicting with other changes because patchwork started serving
invalid diffs during download. Ignore this false positive red check.
You may also no longer be able to use computationally-expensive
functionality within patchwork without logging in. This AFAIU is
supposed to help with AI scraper-induced overloads.
reply other threads:[~2026-09-08 22:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260908155640.02d96800@kernel.org \
--to=kuba@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