今日重点:🗣️ 口语——V4L2 维护者 Hans Verkuil 昨晚在 linux-media 对一个汽车场景的 RFC 连 push 三轮, 提案方 Maxime Ripard 从「That's very arguable?」硬顶,到「Yeah, I guess that could work / ACK. Thanks!」软化接受。 五个回合、五种「说话动作」,每一个都是评审会上能直接搬用的模板——定调、挑战前提、锚定契约、软化让步、澄清立场。 素材:[PATCH RFC 0/5] media: Fault-Tolerant V4L2 的完整评审对话链(11-10 20:08 ~ 22:44 北京,5 封邮件全部带 lore 链接可溯源)。

🗣️ 现场:一个被反复提起的老问题

/ section

背景:Mattijs Korpershoek 给 V4L2 提了一个「容错」改造——汽车场景里后视/环视摄像头可能在行驶中被磕坏或掉线, 但今天的 V4L2 框架假设「pipeline 里所有实体必须在场」,一颗 camera 坏了整条 pipeline 起不来。 这个改动在 Prague 的 Linux Plumbers Camera & ISP unconference 讨论过,落地成 RFC 后, 维护者 Hans Verkuil 把一个他反复提了多年的老问题又甩回桌面:userspace 怎么知道这条 pipeline 允许「部分可用」? 提案方 Maxime Ripard 接招。下面五段全部逐字摘自真实邮件,来源附 lore 链接,点开可对照。

🗣️ 五个动作

/ section

① Hans R1 · 定调:把「老问题」单句成段甩回桌面。
原句:We've been discussion Fault Tolerant V4L2 for many years now, and every time I raise this issue, but I never received any proposals. / This must be solved.
语境翻译:Fault-Tolerant V4L2 这事我们讨论好多年了,每次我都提这个问题,但从来没收到过任何方案。/ 这事必须解决。
要点:Hans 先把「这不是第一次提」挂在前面——every time I raise this issue 把个人不满升格为历史悬案, 然后 This must be solved. 一句话单独成段。这个排版本身就是态度: 短句独立成段在英文邮件里 = 拍桌子。注意他用 must 不是 should,用被动 be solved 不指名要谁解决—— 把「这事必须办」和「你来办」分开,既表决心又不得罪人。
复述引导:合上原文,10 秒内说一句:We've been discussion [主题] for many years now, and every time I raise this issue, but I never received any proposals. This must be solved.
来源:Hans Verkuil,11-10 20:08 北京

② Maxime R1 · 挑战前提:一个词的反问 + 一串类比反例。
原句:That's very arguable? We have plenty of other examples where we allow to show a software representation of something that isn't available in hardware, starting with virtually any memory buffer allocation, but also disabled CPUs, swapped pages, etc. ... It's a circular dependency that cannot be solved on a per-device basis.
语境翻译:这很可议吧?我们有的是反例——软件层表示一个硬件上不存在的东西,几乎所有内存缓冲区分配都是这样,还有被关掉的 CPU、被换出的页,等等。……这是个循环依赖,按单设备维度根本解不开。
要点:Hans 说「This is typically exactly what you want」(现状通常就是你想要的),Maxime 不吵长句, 用 That's very arguable? 一个反问顶回去——arguable 在这里不是「可争论」,是「站不住脚」, 配合问号语调上扬,书面里读出来说就是「你确定吗?」。紧跟着 plenty of other examples 三串类比 (内存分配、disabled CPU、swapped pages),让对方必须为「为什么 V4L2 特殊」举证。 最狠的一击是收尾:It's a circular dependency that cannot be solved on a per-device basis. ——不跟你辩方案,直接指出你的两个要求互相矛盾。
复述引导:说一句「That's very arguable? We have plenty of other examples where [反例领域], starting with [最近的一个], but also [其他两个]. [对方两个要求] is a circular dependency that cannot be solved on [对方假设的维度].」——三个类比必须真的存在,不能临时编。
来源:Maxime Ripard,11-10 20:33 北京

③ Hans R2 · 锚定契约:先承认现状、再警告「contract breaks」。
原句:It's simply how V4L2 works today: video devices do not appear until all components are instantiated. ... If we add fault tolerance, and you allow video devices to appear even if they are not functioning (or partially functioning), then that contract breaks.
语境翻译:这就是 V4L2 今天的工作方式:video device 直到所有组件都就位才会出现。……如果我们加了容错,你让 video device 在没完全工作(或部分工作)的情况下就出现,那这份契约就破了。
要点:被反问「that's arguable」之后,Hans 不急躁也不退缩,用 It's simply how V4L2 works today 稳住阵脚—— simply 是关键词,暗示「这不是我的个人偏好,是既定事实」。 然后抛出全场最重的一词:that contract breaks。把「video device 出现 = 可用」从「实现细节」升格为 内核与 userspace 之间的契约——契约一改,所有现存应用都要重新验证。 这是内核评审里维护者最强的牌:把讨论从「能不能做」拉到「破坏了什么契约」。
复述引导:说一句「It's simply how [子系统] works today: [一句话描述现状契约]. If we [对方提议的改动], then that contract breaks.」——contract 这个词在内核评审语境里分量很重,别滥用,留给真的会破坏 uAPI 假设的场景。
来源:Hans Verkuil,11-10 21:30 北京

④ Maxime R2 · 软化让步:一个词的「Ish.」+ 给出具体接受路径。
原句:Ish. The only safe assumption you can make about this is that it was functional at probe time. Anything after that is very much up in the air. ... Yeah, I guess that could work ... ACK. Thanks!
语境翻译:勉强吧。这件事你唯一能下的稳妥假设就是「probe 时它是好的」,那之后的事就都很难说了。……嗯,我猜那应该行得通……ACK,谢谢!
要点:Maxime 开场一个 Ish. 是地道的口语让步——「ish」是英语母语者表示「某种程度上算吧」的后缀, 单独成句相当于中文「emmm 也算吧」,既不承认对方全对,也不硬顶。 中间用 up in the air(悬而未决)这个口语短语继续辩——比 uncertain 更口语化、更有画面。 但关键的「说话动作」在收尾:当 Hans 给出 /sys 具体方案时,Maxime 不再硬顶, 用 Yeah, I guess that could work 软化接受(guess 把「同意」包装成「暂时认同」), 最后用内核专属的最短接受词 ACK. Thanks! 收尾。 这套节奏是「先坚持、再让步、最后明确收下」——比一直硬顶或一开始就认怂都更显工程师素养。
复述引导:说一句「Ish. The only safe assumption you can make about [话题] is [底线]. Anything after that is very much up in the air. ... Yeah, I guess that could work. ACK. Thanks!」——Ish 和 ACK 别漏,前者定调、后者定边界。
来源:Maxime Ripard,11-10 22:17 北京

⑤ Hans R3 · 澄清立场:用「To be clear」把自己从「反对派」救回来。
原句:To be clear: I really want to see Fault Tolerant V4L2 happening. It's clearly very useful for a specific type of use-case. But first we need a solution for this specific uAPI issue.
语境翻译:把话说清楚:我是真心希望 Fault Tolerant V4L2 落地的。它对特定一类用例显然非常有用。但首先,我们得把这个具体的 uAPI 问题解掉。
要点:Hans 连 push 三轮之后,最后用 To be clear: 开头把自己的真实立场摊开—— 我不是反对这件事,我只是坚持先把前置问题解决。 I really want to see X happening 是内核邮件里「支持但严格」的固定句式, really 强调真诚,happening 用动名词强调「落地、发生」而不是纸面方案。 后面 But first 两个字把顺序钉死:先解决我这关,再谈你那关。 评审里最容易被误读的就是「反复 push back = 反对」,Hans 用一句话避免了这个误读—— 这是维护者给提案人留面子的标准动作。
复述引导:说一句「To be clear: I really want to see [对方提案] happening. It's clearly very useful for [具体场景]. But first we need [你坚持的前置条件].」——really want 和 But first 必须都出现,前者澄清动机、后者钉死顺序。
来源:Hans Verkuil,11-10 22:44 北京

尾声:为什么这五回合值得背下来。——内核评审的真功夫不在「你同不同意」,而在「你怎么表达同意与不同意」。 Hans 的三个动作(定调 / 锚定契约 / 澄清立场)和 Maxime 的两个动作(挑战前提 / 软化让步)合起来, 是一场「有立场、有底线、又留面子」的完整示范。下次你被维护者 push back,或被新人 proposal 顶到, 这五个句式可以照单全收。

✨ 辅助彩蛋:四个能直接搬上会的短语

/ section

★ 反问、循环、澄清、悬着——四个短语各管一件事

都出自真实评审邮件,不是仿写

① That's very arguable? 书面里的反问,相当于「你确定吗 / 这站不住脚吧」。比 I disagree 更轻、比 That's wrong 更给面子。 原文:Maxime 回应 Hans 的「This is typically exactly what you want」时一句话顶回。
② circular dependency 循环依赖——指出对方两个要求互相矛盾的杀手锏。 原文:It's a circular dependency that cannot be solved on a per-device basis. 在内核语境里专指「你既要 A 又要 B,但 A 和 B 互相卡住」。
③ up in the air 悬而未决、说不准。地道口语,比 uncertain 更画面化。 原文:The only safe assumption you can make about this is that it was functional at probe time. Anything after that is very much up in the air.
④ To be clear 把话说清楚——用来澄清自己被误读的立场,常放在段落最开头。 原文:To be clear: I really want to see Fault Tolerant V4L2 happening. 是「我不是反对,只是坚持先做 X」的固定开场。
记忆钩子 arguable 反问、circular 拆矛盾、up in the air 说悬、to be clear 洗立场。
溯源 ①④出自 Maxime R1 与 Hans R3; ②同 Maxime R1;③出自 Maxime R2。
和你相关 下次评审会上被反复 push back 时,用「To be clear」先澄清自己;被提案顶到时,用「That's very arguable?」反问前提——比直接说「我不同意」更专业。

✍️ 今日练习

/ column
✍️ 场景:你在评审会上推一个新 uAPI 设计,维护者连续两轮 push back:第一轮说「It's simply how X works today. If we do this, then that contract breaks.」第二轮说「This must be solved.」你有 60 秒口头回应。要求三句话:第 1 句用 That's very arguable 挑战他的现状前提,并给一个真实存在的反例类比;第 2 句用 circular dependency 指出他两个要求互相矛盾;第 3 句软化收尾,给出你的具体方案(必须用 Yeah, I guess ... could work 或类似软化句式),并反问「How would that not work?」。不许用 I think、I feel、maybe 开头。
💡 显示答案
参考作答(仿写示范,非原文):That's very arguable? We have plenty of other examples where a device appears even if parts of it are not yet ready, starting with USB root hubs, but also disabled CPUs and swapped pages. You are asking us at the same time to not create the device and to let the application signal to that device that it can be created — that's a circular dependency that cannot be solved on a per-device basis. Yeah, I guess a sysfs entry like v4l-fault-tolerance could work — applications opt in by writing 1 to it. How would that not work? 讲法要点:第 1 句反问要短促上扬,类比必须是真实存在的(USB root hub / disabled CPU 都是 Hans 邮件里 Maxime 用过的);第 2 句必须明确点出对方的两个具体要求,然后才能定性为 circular dependency;第 3 句 Yeah, I guess 把「接受」包装成「暂时同意」,How would that not work? 把举证责任还给维护者——这是 Maxime 在原对话里用过的同一招。
📖 原文:That's very arguable? We have plenty of other examples where we allow to show a software representation of something that isn't available in hardware, starting with virtually any memory buffer allocation, but also disabled CPUs, swapped pages, etc. ... It's a circular dependency that cannot be solved on a per-device basis. ... Yeah, I guess that could work ... ACK. Thanks! ... How would that not work?
📎 原文引用

每日一句:Push back with a reason, concede with a path, clarify with a stance.

仿写示范