ci: drop outdated 6.6 / 6.18 ev300_neo rows (kernel 7.0 only)#193
Merged
Conversation
The neo target on EV300 has stabilised on Linux 7.0 — same kernel the rest of the neo family (av300/cv500/cv300/av200/cv200/av100/cv100) also targets. The 6.6 and 6.18 matrix rows were scaffolding for the incremental kernel-bump exercise during V4 neo bring-up and have served their purpose; keeping them in CI now burns ~14 minutes of runner time per push on builds that test code paths nothing else exercises. Removes: - two matrix rows: ev300_neo @ 6.6, ev300_neo @ 6.18 - `Setup neo target (6.6 kernel)` step (60 LoC, synthesised a `hi3516ev300.4.15.config` per CI run and pointed the defconfig at the 6.6 vendor tarball) - `(EV300, 6.18/7.0 kernel)` step renamed to `(EV300, 7.0 kernel)` with its `if:` tightened from `(kernel == '6.18' || kernel == '7.0')` to just `kernel == '7.0'`. Body unchanged — already drove the upstream-patches branch + the committed `hi3516ev300.neo.config`. The synthesised `hi3516ev300.4.15.config` was ephemeral (no file in firmware repo), so no cross-repo cleanup is needed. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The neo target on EV300 has stabilised on Linux 7.0 — same kernel the rest of the neo family (av300 / cv500 / cv300 / av200 / cv200 / av100 / cv100) also targets. The 6.6 and 6.18 matrix rows were scaffolding for the incremental kernel-bump exercise during V4 neo bring-up and have served their purpose; keeping them in CI now burns ~14 minutes of runner time per push on builds that test code paths nothing else exercises.
Removes:
ev300_neo @ 6.6,ev300_neo @ 6.18Setup neo target (6.6 kernel)step (60 LoC — synthesised ahi3516ev300.4.15.configper CI run and pointed the defconfig at the 6.6 vendor tarball)(EV300, 6.18/7.0 kernel)step renamed to(EV300, 7.0 kernel)with itsif:tightened from(kernel == '6.18' || kernel == '7.0')to justkernel == '7.0'. Body unchanged — already drove the upstream-patches branch + the committedhi3516ev300.neo.config.The synthesised
hi3516ev300.4.15.configwas ephemeral (no file in firmware repo), so no cross-repo cleanup is needed.Test plan
6.6,6.18,4.15, orhi3516ev300.4.15.configreferences remain(EV300, 7.0 kernel)step body matches the prior(EV300, 6.18/7.0 kernel)body verbatim — no behavioural change for the surviving 7.0 path🤖 Generated with Claude Code