今日重点：📖 阅读——今天 linux-media 上来了一份稀有材料：因斯布鲁克大学学生 Christian Koever-Draxl 把 Amlogic S4 的整条 BSP 栈推上游，cover letter 里写了一段 AI 协作披露——坦白说自己大量用了 Claude Code，同时把「AI 干的活」和 「人担的责」切得清清楚楚。这种披露 2026 年起内核社区开始要求 （Documentation/process/generated-content.rst），他这段写法几乎是模板。 精读一遍，你以后写任何 AI 辅助的贡献说明都能用。

📖 阅读：四句话的披露段

/ section
This work was done with the help of an AI coding assistant, Claude (Anthropic), used through Claude Code over many sessions. It did a large part of the hands-on work: it read the vendor kernel and the firmware interfaces, probed registers on the board, drafted the code and the changelogs, and ran the builds, checkpatch, dt_binding_check and the tests on the hardware. I directed the work, reviewed every change and the final patches, and take responsibility for them. There is no single prompt to quote; the sessions were of the form "find out why X fails on this board, fix it, test it on the box".

这段四句话的披露，结构就是「承认 → 分工 → 担责 → 答疑」。 第一句承认事实：用被动式 This work was done with the help of ... 把 AI 直接摆上台面，括号注明公司（Anthropic）与工具（Claude Code），「over many sessions」 交代这不是一次性问答，而是长期协作。 第二句切分工：主语换成 It（指 AI），冒号引出四个并列动词—— read / probed / drafted / ran——全是「动手类」动作；关键定语是 hands-on work（动手活、操作层的工作），这是整段最关键的措辞， 把 AI 的贡献精确限定在「操作」层，不是「决策」层。

第三句换人出场：主语从 It 切到 I—— I directed the work, reviewed every change and the final patches, and take responsibility for them。三个动词 directed / reviewed / take responsibility 一个比一个重，刚好对应「指导 → 审查 → 担责」三层。 整段的法律/伦理重量全压在这句上——告诉维护者：补丁是我签的，问题找我。 第四句预防性答疑：预料到读者会问「那 prompt 是什么」，直接堵回去—— There is no single prompt to quote（没有一条单一 prompt 可以引用）， 分号后给出原因：session 的形态是「找出为什么 X 在这块板子上失败、修掉、在机器上测试」。 这一刀把「会不会是 AI 一键生成」的怀疑拆干净了。

★ 句式与语汇拆解

同段落 · 四个值得抄的写法

with the help of X（在 X 的协助下） with the help of an AI coding assistant —— 正式场合致谢/披露的标准开头。help 暗示「辅助不是替代」，比 using AI 的语气更稳妥。套用到自己的工作：This series was prepared with the help of <工具名>。
hands-on work（动手活） 直译「手上的工作」，专指操作性、执行性的事——读代码、探寄存器、写草稿、跑构建。反义是 design/decision（设计/决策）。把 AI 的贡献归到 hands-on，等于在分工层面降级——这是这段披露能立住的关键。
directed / reviewed / take responsibility（三层递进） 三个动词排成「指导 → 审查 → 担责」的递进——direct 在下，review 在中，responsibility 收尾。少了任何一层披露都不完整：光说 I directed 显得指挥不动手，光说 I reviewed 显得流于形式，必须有 take responsibility 才算数。
There is no single X to quote（没有单一 X 可引用） 预防性答疑的高情商说法——预判到读者会问「给我看看 prompt」，先承认做不到，再用分号给出原因。这个句式可以推广到任何「答案不是单点」的场景：There is no single commit to revert; the regression came from a combination of ...

🔗 原文

✨ 辅助彩蛋（术语卡）

/ column

★ bit-exact / bit-exactness（位精确）

同 cover letter 前一段 · 验证方法论

原文 Bit-exactness was checked against ffmpeg/libavcodec frame by frame for H.264, VP9, AV1 and HEVC conformance and real-world streams; MPEG-2 differs by the hardware's IDCT rounding.
中文 位精确（逐位一致）——视频解码器输出的每一个比特都和参考实现完全一致。codec 测试里的最高标准：哪怕一帧差一个比特都算 fail。cover letter 用 frame by frame（逐帧）强调比对的粒度。
为什么单独讲 作者还顺手做了一个诚实的反例：MPEG-2 differs by the hardware's IDCT rounding——MPEG-2 不 bit-exact，原因是硬件的 IDCT 舍入差。codec 评审里这种「主动报告不一致项」比宣称全过更赢得信任。
和你相关 和你相关：做 V4L2 / codec 驱动时，bit-exact 是评审必问的关键词。能写出「which streams are bit-exact and which are not, and why」的 cover letter，比堆测试日志管用十倍。

🔗 原文

✍️ 今日练习

/ column
✍️ 读后仿写：假设你用 AI 助手调试了一个 camera 传感器的 V4L2 驱动（AI 帮你读 datasheet、生成 init table 草稿、跑 v4l2-compliance；你负责定调试方向、review 寄存器序列、对最终补丁负责），现在要在 cover letter 里加一段 AI 协作披露。要求：① 用 with the help of X 开头承认；② 用 hands-on work + 并列动词列分工；③ 用 I directed / reviewed / take responsibility 收尾；④ 用 There is no single X to quote 预防性答疑。整段不超过 5 句英文。
💡 显示答案
参考（仿写示范，非原文）：This work was done with the help of an AI coding assistant, used through many interactive debugging sessions. It did a large part of the hands-on work: it read the sensor datasheet, drafted the init register table, and ran v4l2-compliance on the board. I directed the debugging, reviewed every register write against the datasheet, and take responsibility for the final patches. There is no single prompt to quote; the sessions were of the form 'capture a frame, compare against the reference, find what is off'.
📖 原文：This work was done with the help of an AI coding assistant, Claude (Anthropic), used through Claude Code over many sessions. It did a large part of the hands-on work: it read the vendor kernel and the firmware interfaces, probed registers on the board, drafted the code and the changelogs, and ran the builds, checkpatch, dt_binding_check and the tests on the hardware. I directed the work, reviewed every change and the final patches, and take responsibility for them. There is no single prompt to quote; the sessions were of the form 'find out why X fails on this board, fix it, test it on the box'.
📎 原文引用

Admit it, split the labor, own the result, preempt the follow-up — four sentences is all a disclosure needs.

素材：lore.kernel.org linux-media · Amlogic S4 vdec cover letter（Christian Koever-Draxl，〔10-25 19:25 UTC〕）· 内核英语 · 每日一篇