On 09/04/2025 2:28 pm, Marek Marczykowski-Górecki wrote: > On Wed, Apr 09, 2025 at 02:05:05PM +0100, Andrew Cooper wrote: >> Linux 6.6.56 was already added to test-artifacts for the argo testing, and >> this removes one moving part while cleaning things up. >> >> Drop the associated export job, and dockerfile. > My hw12 runner series adds CONFIG_USB_RTL8152, there are also other > series that needs extending kernel config. Is there some better way of > handling such series than sending patches to two repositories? Maybe > test-artifacts.git scripts could pull some parts from xen.git? But the > committing order would still be weird (commit kernel change into > xen.git, rebuild test-artifacts, commit the rest to xen.git)...
Yes, I'm aware. I'm trying to get us down to 1 way of doing artefacts, rather than continuing the hybrid scheme. I have a *lot* of changes to test-artefacts to post too. When that's done, updating the config (or another aspect of the artefact) should just be a change to test-artefacts, with no change to Xen. Updating the versions will require a patch to test-artefacts first, then one to Xen to start using it. > >> Signed-off-by: Andrew Cooper <[email protected]> >> --- >> CC: Anthony PERARD <[email protected]> >> CC: Stefano Stabellini <[email protected]> >> CC: Michal Orzel <[email protected]> >> CC: Doug Goldstein <[email protected]> >> CC: Marek Marczykowski-Górecki <[email protected]> >> >> https://gitlab.com/xen-project/hardware/xen-staging/-/pipelines/1760198654 > This still waits in the queue for adl and kbl. But should be good, given > it worked also with 6.12. > It worked in local smoke tests too. ~Andrew
