# git rev-parse -q --verify 1548b060d6f32a00a2f7e2c11328205fb66fc4fa^{commit} # git fetch -q -n -f git://fs.ozlabs.ibm.com/kernel/linus master # git rev-parse -q --verify 1548b060d6f32a00a2f7e2c11328205fb66fc4fa^{commit} 1548b060d6f32a00a2f7e2c11328205fb66fc4fa # git checkout -q -f -B kisskb 1548b060d6f32a00a2f7e2c11328205fb66fc4fa # git clean -qxdf # < git log -1 # commit 1548b060d6f32a00a2f7e2c11328205fb66fc4fa # Merge: e56b2b605799 ad6bfe1b66a5 # Author: Linus Torvalds # Date: Sun Sep 10 11:55:26 2023 -0700 # # Merge tag 'topic/drm-ci-2023-08-31-1' of git://anongit.freedesktop.org/drm/drm # # Pull drm ci scripts from Dave Airlie: # "This is a bunch of ci integration for the freedesktop gitlab instance # where we currently do upstream userspace testing on diverse sets of # GPU hardware. From my perspective I think it's an experiment worth # going with and seeing how the benefits/noise playout keeping these # files useful. # # Ideally I'd like to get this so we can do pre-merge testing on PRs # eventually. # # Below is some info from danvet on why we've ended up making the # decision and how we can roll it back if we decide it was a bad plan. # # Why in upstream? # # - like documentation, testcases, tools CI integration is one of these # things where you can waste endless amounts of time if you # accidentally have a version that doesn't match your source code # # - but also like the above, there's a balance, this is the initial cut # of what we think makes sense to keep in sync vs out-of-tree, # probably needs adjustment # # - gitlab supports out-of-repo gitlab integration and that's what's # been used for the kernel in drm, but it results in per-driver # fragmentation and lots of duplicated effort. the simple act of # smashing an arbitrary winner into a topic branch already started # surfacing patches on dri-devel and sparking good cross driver team # discussions # # Why gitlab? # # - it's not any more shit than any of the other CI # # - drm userspace uses it extensively for everything in userspace, we # have a lot of people and experience with this, including # integration of hw testing labs # # - media userspace like gstreamer is also on gitlab.fd.o, and there's # discussion to extend this to the media subsystem in some fashion # # Can this be shared? # # - there's definitely a pile of code that could move to scripts/ if # other subsystem adopt ci integration in upstream kernel git. other # bits are more drm/gpu specific like the igt-gpu-tests/tools # integration # # - docker images can be run locally or in other CI runners # # Will we regret this? # # - it's all in one directory, intentionally, for easy deletion # # - probably 1-2 years in upstream to see whether this is worth it or a # Big Mistake. that's roughly what it took to _really_ roll out solid # CI in the bigger userspace projects we have on gitlab.fd.o like # mesa3d" # # * tag 'topic/drm-ci-2023-08-31-1' of git://anongit.freedesktop.org/drm/drm: # drm: ci: docs: fix build warning - add missing escape # drm: Add initial ci/ subdirectory # < /opt/cross/kisskb/korg/gcc-12.2.0-nolibc/mips-linux/bin/mips-linux-gcc --version # < /opt/cross/kisskb/korg/gcc-12.2.0-nolibc/mips-linux/bin/mips-linux-ld --version # < git log --format=%s --max-count=1 1548b060d6f32a00a2f7e2c11328205fb66fc4fa # make -s -j 160 ARCH=mips O=/kisskb/build/linus-rand_allnoconfig_mips-gcc12 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-12.2.0-nolibc/mips-linux/bin/mips-linux- allnoconfig # < make -s -j 160 ARCH=mips O=/kisskb/build/linus-rand_allnoconfig_mips-gcc12 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-12.2.0-nolibc/mips-linux/bin/mips-linux- help # make -s -j 160 ARCH=mips O=/kisskb/build/linus-rand_allnoconfig_mips-gcc12 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-12.2.0-nolibc/mips-linux/bin/mips-linux- olddefconfig # make -s -j 160 ARCH=mips O=/kisskb/build/linus-rand_allnoconfig_mips-gcc12 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-12.2.0-nolibc/mips-linux/bin/mips-linux- Completed OK # rm -rf /kisskb/build/linus-rand_allnoconfig_mips-gcc12 # Build took: 0:00:25.748902