Skip to content
Skills Library
Programming · Analysis

patch-status

/patch-status

Check the acceptance state of a Linux kernel patch in patchwork and decide the correct next action — wait, repost, or ask. TRIGGER — invoke when the task is to find out whether a submitted kernel patch or series was accepted, rejected, or needs changes, or whether it is time to ping the maintainers. DO NOT TRIGGER for reading the review discussion itself (use lkml:lore) or for sending anything (use lkml:reply or lkml:submit).

Repository
ccc ↗
Licence
BSD-3-Clause
Last repository change
04.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 04.10.2026, without references to retired models or APIs.

Licence

BSD-3-Clause, otwarta.

What it does and when to use it

Check the acceptance state of a Linux kernel patch in patchwork and decide the correct next action — wait, repost, or ask. TRIGGER — invoke when the task is to find out whether a submitted kernel patch or series was accepted, rejected, or needs changes, or whether it is time to ping the maintainers. DO NOT TRIGGER for reading the review discussion itself (use lkml:lore) or for sending anything (use lkml:reply or lkml:submit).

Arguments

/patch-status [Message-ID | patchwork URL]
Original author description

Check the acceptance state of a Linux kernel patch in patchwork and decide the correct next action — wait, repost, or ask. TRIGGER — invoke when the task is to find out whether a submitted kernel patch or series was accepted, rejected, or needs changes, or whether it is time to ping the maintainers. DO NOT TRIGGER for reading the review discussion itself (use lkml:lore) or for sending anything (use lkml:reply or lkml:submit).

How it works

  1. Query by Message-ID
  2. What the states mean
  3. When silence means "wait" and when it means "act"
Original SKILL.md headings · 40 lines, 539 words
SKILL.md preview
---
name: patch-status
description: Check the acceptance state of a Linux kernel patch in patchwork and decide the correct next action — wait, repost, or ask. TRIGGER — invoke when the task is to find out whether a submitted kernel patch or series was accepted, rejected, or needs changes, or whether it is time to ping the maintainers. DO NOT TRIGGER for reading the review discussion itself (use lkml:lore) or for sending anything (use lkml:reply or lkml:submit).
argument-hint: "[Message-ID | patchwork URL]"
---

Patchwork tracks what maintainers will do with a patch; the mailing list tracks what people said about it. Check both before concluding anything: a thread with zero replies can still be `accepted`, and a thread full of praise can sit at `changes-requested`.

## Query by Message-ID

```bash
curl --silent "https://patchwork.kernel.org/api/1.2/patches/?project=netdevbpf&msgid=<message-id>" | jq '.[0] | {state, delegate: .delegate.username, web: .web_url}'
```

- `<message-id>` is bare, without angle brackets — the ID of a **patch mail** (`1/N`, `2/N`, ...). Cover letters are not patches; querying a `0/N` ID returns an empty list.
- `project=netdevbpf` covers netdev and bpf. Other kernel subsystems have their own project slugs on the same instance — list them via `https://patchwork.kernel.org/api/1.2/projects/` and match by `list_email`. Some subsystems do not use patchwork at all; an empty result for every patch of a series means look at the thread and the maintainer's git tree instead.
- Other projects run their own instances with the same API (U-Boot lives on `patchwork.ozlabs.org`, `project=uboot`).

## What the states mean

| state | meaning | your move |
| --- | --- | --- |
| `new` | in the queue, nobody triaged it | wait |
| `under-review` | a maintainer is looking | wait |
| `changes-requested` | review asked for changes | answer every comment in-thread, then new version as a new thread |
| `superseded` | a newer version of the series replaced it | check the newest version instead |
| `accepted` / `queued` | applied to the maintainer tree | done; netdev also sends an "applied" mail to the thread |
| `rejected` / `not-applicable` | will not be taken as-is | read the thread for the reason before doing anything |
| `deferred` / `awaiting-upstream` | parked on something external | find what it waits for in the thread |

`delegate` set to a maintainer (e.g. `netdev`) means the series is in that queue — a good sign, not a request for action.

A reply in the thread reading `pw-bot: cr` (or `pw-bot: changes-requested`) is a bot command that moved the series to `changes-requested`. Treat it exactly like the state: the next posting is a new version in a new thread, never a reply with fixed patches.

## When silence means "wait" and when it means "act"

Kernel review runs on timers, and pinging early reads as pressure:

- netdev moves in days; most other subsystems in one to two weeks; anything overlapping a merge window slows down further.
- Wait at least one week of silence before nudging anywhere, and longer around a merge window. For slower trees (staging, individual driver maintainers), two to three weeks of silence is normal.
- A bare "ping" or "bump" reply is explicitly called rude in the netdev process docs. A nudge must carry content: state your understanding of where things stand and ask one concrete question — "X asked for A in v2 and that discussion stalled; should I go with B and repost?".
- If the state is `changes-requested`, silence is on your side of the net: nothing will happen until a new version is posted.

Report findings to the user as: state, who (if anyone) replied since the last check, and the single recommended next action.

Versions

The database has no other skills named patch-status.

Database snapshot: 13.11.2026 · package version af1da10f48e0 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100etiquette
    Reference for the communication rules of Linux kernel mailing lists — who to write to, what goes where, timing, tags, and tone. TRIGGER — invoke when deciding where or to whom a kernel question, bug report, or patch should go, when unsure whether a planned action (ping, resend,…
  • 100lore
    Read, search, and monitor Linux kernel mailing-list threads on lore.kernel.org. TRIGGER — invoke when a task involves fetching a kernel thread, checking whether reviewers replied to a submission, sweeping all tracked submissions for news ("check the lists", "any replies?"),…
  • 100kernel-lore-hunter
    追踪 Linux 内核补丁与讨论——从一篇文章、一个 commit、一个分支名、一个符号名或一个话题出发,定位对应的 patchset、LKML/linux-mm/linux-fsdevel 邮件串、维护者 git 分支,并判断版本与是否已合并。Use when the user gives an article, commit hash, branch name, kernel symbol (e.g. PG_rcu_free, filemap_read_rcu_batch) or topic and asks for "the patchset",…
  • 100kernel-lore-search
    Search kernel mailing lists via lore git mirrors. Use when checking prior art before a report, verifying a quote, or finding a sent message.
  • 100patchwork
    Edit a FileMaker (.fmp12) file directly: add or change fields, scripts and script steps, value lists, custom functions, layouts and themes, through Patchwork and Claris FMUpgradeTool, on a versioned working copy. Use when the user asks to change, build, fix or explore a FileMaker solution.
  • 100kernel-repro-harness
    Standalone kernel reproducer maintainers can rerun: syscall loop, controls, loop images, OrbStack then GCP. Use when reducing an app's kernel bug.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.