Fimeg/SouveraineOS
Watch
1
0
Fork
You've already forked SouveraineOS
 0
Code Releases Activity

docs: record SLIMbus v1 submission

Browse source
This commit is contained in:
Casey Tunturi 2026-08-07 20:40:16 -04:00
commit 376ef95218
1 changed files with 13 additions and 22 deletions
Download patch file Download diff file Expand all files Collapse all files

35
docs/davids-tasks/slimbus-def-act-chan.md
View file

@ -1,14 +1,17 @@
# SLIMbus `DEF_ACT_CHAN` upstream follow-up
Status: David Heidelberg reviewed the prepared branch. His requested changes
are applied. Nothing has been sent upstream.
Status: v1 was sent upstream on 2026-08-07 after David Heidelberg's review.
Awaiting public review.
## Prepared work
## Submission record
- Original `linux-blueline` commit under review: `3ceab71eded0`
- Review branch: [`b4/slimbus-def-act-chan`](https://gitea.wiuf.net/Fimeg/linux-blueline/src/branch/b4/slimbus-def-act-chan)
- Prepared patch commit: `4d23acca3a6d`
- [Prepared patch artifact](https://gitea.wiuf.net/Fimeg/Pixel3Arch/src/branch/main/upstream/standalone/slimbus-def-act-chan-v1/0001-slimbus-qcom-ngd-ctrl-match-downstream-def_act_chan-encoding.patch)
- [Public v1 thread](https://patch.msgid.link/20260807-slimbus-def-act-chan-v1-1-fd542efb3d30@samaritansolutions.net)
- Message-ID: `20260807-slimbus-def-act-chan-v1-1-fd542efb3d30@samaritansolutions.net`
- Sent tag: `sent/20260807-slimbus-def-act-chan-b70e4fb7abb1-v1`
- Sent-tag patch commit: `0017d8996c10`
- Current [`b4/slimbus-def-act-chan`](https://gitea.wiuf.net/Fimeg/linux-blueline/src/branch/b4/slimbus-def-act-chan) branch: automatically rolled to v2
- [Saved v1 patch artifact](https://gitea.wiuf.net/Fimeg/Pixel3Arch/src/branch/main/upstream/standalone/slimbus-def-act-chan-v1/0001-slimbus-qcom-ngd-ctrl-match-downstream-def_act_chan-encoding.patch)
- Upstream base recorded by `b4`: `55f2ea9ff83c`
- Public identity: `Casey Tunturi <casey@samaritansolutions.net>`
@ -65,21 +68,7 @@ three local-tree limitations. They are not findings against the patch.
Never infer or invent a tag or David's preferred email address.
Because v1 has not been sent, changes made during this private review remain
v1 rather than becoming v2.
## Submission sequence
Only continue when Casey asks.
1. If David sends further feedback or an exact tag, apply it and refresh the
saved patch and Gitea review branch.
2. Configure or authenticate `b4` for
`casey@samaritansolutions.net`.
3. Run `b4 send --reflect` and inspect the copy delivered only to Casey.
4. After Casey explicitly approves the reflected message, run `b4 send`.
The prepared routing is:
The submitted routing was:
- To: Srinivas Kandagatla `<srini@kernel.org>`
- Cc: `linux-arm-msm@vger.kernel.org`
@ -88,11 +77,13 @@ The prepared routing is:
- Cc: `phone-devel@vger.kernel.org`
- Cc: `stable@vger.kernel.org`
After submission:
## Upstream follow-up
- If applied, record the maintainer-tree commit and later mainline commit.
- If changes are requested, amend the branch, record a short changelog, and
send v2.
- If nobody responds, wait at least one week before a polite ping or resend.
- Do not send the automatically prepared v2 unless upstream review requires a
change.
Reference: [Linux kernel patch submission guide](https://docs.kernel.org/process/submitting-patches.html)