messages from 2026-11-06 09:36:32 to 2026-11-12 20:25:54 UTC [more...]
[PATCH v5 0/6] agents: add skills for Fixes tags, stable tags, similar bugs, and commit messages
2026-11-12 20:25 UTC (25+ messages)
` [PATCH v5 1/6] agents: add infrastructure for agent resources
` [PATCH v5 2/6] agents: add a skill to determine Fixes tags
` [PATCH v5 3/6] agents: add a skill to determine stable tags
` [PATCH v5 4/6] agents: add a skill to find other instances of a fixed bug
` [PATCH v5 5/6] agents: add a skill to write commit messages
` [PATCH v5 6/6] agents: add a skill to write KUnit tests
[PATCH v3] docs: submitting-patches: Clarify partial review tags
2026-11-12 14:48 UTC (4+ messages)
[PATCH] docs: cve: Describe how security fixes reach users
2026-11-11 6:57 UTC (3+ messages)
[PATCH RESEND] wifi: ath11k: release the rproc reference on teardown
2026-11-11 6:43 UTC (6+ messages)
[PATCH v2] docs: submitting-patches: Clarify half-baked review tags
2026-11-09 23:44 UTC (3+ messages)
[PATCH] docs: remove Assisted-by references
2026-11-09 23:23 UTC (11+ messages)
[PATCH 00/14] security-bugs doc updates
2026-11-09 17:32 UTC (17+ messages)
` [PATCH 01/14] docs: security-bugs: reorganize the document without changing its contents
` [PATCH 02/14] docs: security-bugs: clarify when to Cc the security team
` [PATCH 03/14] docs: security-bugs: never publish reproducers of bugs with a security impact
` [PATCH 04/14] docs: threat-model: clarify the case of automatically mounted file systems
` [PATCH 05/14] docs: security-bugs: explain how to send a fix that can be applied
` [PATCH 06/14] docs: security-bugs: do not send archives or binary attachments
` [PATCH 07/14] docs: security-bugs: first-time reporters must send a single report first
` [PATCH 08/14] docs: security-bugs: explain what to do when a report gets no response
` [PATCH 09/14] docs: security-bugs: reports left unanswered for 7 days will be dropped
` [PATCH 10/14] docs: security-bugs: add a section for maintainers receiving reports
` [PATCH 11/14] docs: security-bugs: explain why directly sent reports add extra work
` [PATCH 12/14] docs: security-bugs: explain why AI-found bugs are handled publicly
` [PATCH 13/14] docs: submitting-patches: defer to security-bugs.rst for security fixes
` [PATCH 14/14] docs: netdev: align the security fixes section with security-bugs.rst
[PATCH] Documentation: kunit: document --summary and --failed options
2026-11-08 22:07 UTC (4+ messages)
` [PATCH v2] "
[PATCH] docs: checkpatch: Fix DEVICE_ATTR_WO macro name
2026-11-08 2:18 UTC (2+ messages)
[PATCH] doc: process: clarify legacy status of applying-patches and point to Git
2026-11-07 8:10 UTC (3+ messages)
[PATCH v5] doc: process: clarify scope of applying-patches as legacy reference
2026-11-06 9:36 UTC (2+ messages)
page: | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox