Jorijn van der Graaf
339f4b9b40
Beside the push gates, crafter-review runs the pre-send review of a kernel contributor's workbench: --mode series over a format-patch export with its cover letter, --mode reply over a mail draft. The inventory partitions a cover letter, a plain mail and the camera review's shape; ten kernel lenses join the table with their gates (structure, code, artifact truth) and the persona gate - one maintainer-persona instance per --reviewers entry, its whole pass gating its blocks and pruning the units that are not theirs. A series' code units are keyed on the code like the push gates'; every text unit on its text, the references it cites and the anchor when it is dated. The references an artifact cites are prefetched through utilities/lore.py into the gate-state, with a digest in the run layer, and a persona's calibration map is its lore listing. The kernel schema carries the persona vocabulary, the kernel note kinds, the predicted review and the not-mine list; the matrix the persona holes, the thin and the modelled units; gates clean without a persona pass is GATES CLEAN. A reply's gate-state sits beside the draft and is read once; a kernel mode needs --subsystem, defaults the effort to max and the trees to work/linux,work/milos-linux, and excuses no unit from the holes. The kernel lenses and the common text ship verbatim; the table lists them after the push gates' lenses and the config template holds them off, so a repository that never turns them on changes nothing. Prompts, keys and plans were checked byte for byte against the pipeline these modes replace, on its own artifacts: two replies and a series, every system prompt, user prompt, job and reuse key identical.
22 lines
731 B
Text
22 lines
731 B
Text
From: Jorijn van der Graaf <jorijnvdgraaf@catcrafts.net>
|
|
To: Some Maintainer <maintainer@example.org>
|
|
Cc: linux-example@vger.kernel.org
|
|
Subject: Re: [PATCH v2] nfc: widget: add the driver
|
|
In-Reply-To: <20260920.111@example.org>
|
|
References: <20260920.111@example.org>
|
|
|
|
On Sat, 20 Sep 2026 at 10:00, Some Maintainer wrote:
|
|
> The probe should not read the revision twice.
|
|
>
|
|
> Please drop the second read.
|
|
|
|
Agreed, v3 reads it once and keeps it for the attribute.
|
|
|
|
> And the binding needs the example.
|
|
|
|
The example is in 2/2 of v3; it follows [1].
|
|
|
|
[1] https://lore.kernel.org/all/20260815.4567@example.org/
|
|
|
|
Tested-by: Jorijn van der Graaf <jorijnvdgraaf@catcrafts.net>
|
|
Reviewed-by: Jorijn van der Graaf <jorijnvdgraaf@catcrafts.net>
|