Searched +full:debian +full:- +full:build +full:- +full:testing (Results 1 – 16 of 16) sorted by relevance
/linux-6.15/drivers/gpu/drm/ci/ |
D | build.yml | 1 .build: 3 - .container+build-rules 4 stage: build-only 7 - artifacts 9 - FDO_CI_CONCURRENT=${FDO_CI_CONCURRENT} bash drivers/gpu/drm/ci/build.sh 11 .build:arm32: 13 - .build 14 - .use-debian/arm64_build 16 - aarch64 22 .build:arm64: [all …]
|
D | test.yml | 1 .lava-test: 3 - .container+build-rules 6 - !reference [.scheduled_pipeline-rules, rules] 7 - !reference [.collabora-farm-rules, rules] 8 - when: on_success 10 # Note: Build dir (and thus install) may be dirty due to GIT_STRATEGY 11 - rm -rf install 12 - tar -xf artifacts/install.tar 13 - mv -n install/* artifacts/. 14 # Override it with our lava-submit.sh script [all …]
|
D | gitlab-ci.yml | 2 DRM_CI_PROJECT_PATH: &drm-ci-project-path mesa/mesa 3 DRM_CI_COMMIT_SHA: &drm-ci-commit-sha 7d3062470f3ccc6cb40540e772e902c7e2248024 6 TARGET_BRANCH: drm-next 10 DEQP_RUNNER_GIT_URL: https://gitlab.freedesktop.org/mesa/deqp-runner.git 13 FDO_UPSTREAM_REPO: helen.fornazier/linux # The repo where the git-archive daily runs 14 MESA_TEMPLATES_COMMIT: &ci-templates-commit d5aa3941aa03c2f716595116354fb81eb8012acb 16 CI_PRE_CLONE_SCRIPT: |- 17 set -o xtrace 18 …-L --retry 4 -f --retry-all-errors --retry-delay 60 -s ${DRM_CI_PROJECT_URL}/-/raw/${DRM_CI_COMMIT… 19 bash download-git-cache.sh [all …]
|
/linux-6.15/Documentation/bpf/ |
D | s390.rst | 2 Testing BPF on s390 12 2. One-time setup 15 The following is required to build and run the test suite: 23 Debian supports installing compiler and libraries for s390 out of the box. 24 Users of other distros may use debootstrap in order to set up a Debian chroot:: 27 --variant=minbase \ 28 --include=sudo \ 29 testing \ 30 ./s390-toolchain 31 sudo mount --rbind /dev ./s390-toolchain/dev [all …]
|
/linux-6.15/Documentation/rust/ |
D | quick-start.rst | 1 .. SPDX-License-Identifier: GPL-2.0 10 suitable -- the first section below explains this approach. An advantage of this 28 ------------- 36 pacman -S rust rust-src rust-bindgen 39 Debian section in Distributions 42 Debian Testing and Debian Unstable (Sid), outside of the freeze period, provide 45 apt install rustc rust-src bindgen rustfmt rust-clippy 54 dnf install rust rust-src bindgen-cli rustfmt clippy 60 Gentoo Linux (and especially the testing branch) provides recent Rust releases 63 USE='rust-src rustfmt clippy' emerge dev-lang/rust dev-util/bindgen [all …]
|
/linux-6.15/Documentation/admin-guide/ |
D | quickly-build-trimmed-linux.rst | 1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0) 5 How to quickly build a trimmed Linux kernel 8 This guide explains how to swiftly build Linux kernels that are ideal for 9 testing purposes, but perfectly fine for day-to-day use, too. 15 section below: it contains a step-by-step guide, which is more detailed, but 21 self-compiled Linux kernels; install compilers and everything else needed for 24 you then use to configure, build and install your own kernel:: 26 git clone --depth 1 -b master \ 30 # Hint: it's recommended to tag your build at this point. See below for details. 32 # Hint: at this point you might want to adjust the build configuration; you'll [all …]
|
D | verify-bugs-and-bisect-regressions.rst | 1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0) 9 currently supported by developers -- to then explain how to locate the change 22 read and navigate this document -- especially when you want to look something 26 https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html 32 over to the* ':ref:`step-by-step guide <introguide_bissbs>`' *below. It utilizes 45 *segment 2*. Then you can submit a preliminary report -- or continue with 47 full-fledged regression report. In the following example 6.0.13 is assumed to be 51 * **Preparations**: set up everything to build your own kernels:: 55 # * Ensure Secure Boot permits booting self-compiled Linux kernels. 59 git clone -o mainline --no-checkout \ [all …]
|
D | reporting-issues.rst | 1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0) 35 **General remarks**: When installing and testing a kernel as outlined above, 36 ensure it's vanilla (IOW: not patched and not using add-on modules). Also make 44 to pin-point the culprit with a bisection; if you succeed, include its 45 commit-id and CC everyone in the sign-off-by chain. 51 Step-by-step guide how to report issues to the kernel maintainers 58 step-by-step approach. It still tries to be brief for readability and leaves 59 out a lot of details; those are described below the step-by-step guide in a 89 kernel modules on-the-fly, which solutions like DKMS might be doing locally 117 go and install it for the reporting process. Testing and reporting with [all …]
|
D | workload-tracing.rst | 1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0) 7 :Authors: - Shuah Khan <skhan@linuxfoundation.org> 8 - Shefali Sharma <sshefali021@gmail.com> 9 :maintained-by: Shuah Khan <skhan@linuxfoundation.org> 14 * Understanding system resources necessary to build and run a workload 21 `perf <https://man7.org/linux/man-pages/man1/perf.1.html>`_, 22 `stress-ng <https://www.mankier.com/1/stress-ng>`_, 23 `paxtest <https://github.com/opntr/paxtest-freebsd>`_. 30 `strace <https://man7.org/linux/man-pages/man1/strace.1.html>`_ is a 50 How do we gather fine-grained system information? [all …]
|
/linux-6.15/Documentation/virt/uml/ |
D | user_mode_linux_howto_v2.rst | 1 .. SPDX-License-Identifier: GPL-2.0 25 Most OSes today have built-in support for a number of "fake" 27 User Mode Linux takes this concept to the ultimate extreme - there 30 concepts which map onto something provided by the host - files, sockets, 36 The UML kernel is just a process running on Linux - same as any other 57 * You can run a usermode kernel as a non-root user (you may need to 97 your host to build a viable filesystem image. 99 This is extremely easy on Debian - you can do it using debootstrap. It is 100 also easy on OpenWRT - the build process can build UML images. All other 101 distros - YMMV. [all …]
|
/linux-6.15/lib/ |
D | Kconfig.debug | 1 # SPDX-License-Identifier: GPL-2.0-only 19 parameter printk.time=1. See Documentation/admin-guide/kernel-parameters.rst 39 bool "Show build ID information in stacktraces" 42 Selecting this option adds build ID information for symbols in 46 accessible but can be downloaded given the build ID of the vmlinux or 50 int "Default console loglevel (1-15)" 60 Note: This does not affect the log level of un-prefixed printk() 65 int "quiet console loglevel (1-15)" 76 int "Default message log level (1-7)" 82 This was hard-coded to KERN_WARNING since at least 2.6.10 but folks [all …]
|
/linux-6.15/ |
D | CREDITS | 1 This is at least a partial credits-file of people that have 4 scripts. The fields are: name (N), email (E), web-address 6 snail-mail address (S). 10 ---------- 51 D: in-kernel DRM Maintainer 76 E: tim_alpaerts@toyota-motor-europe.com 80 S: B-2610 Wilrijk-Antwerpen 85 W: http://www-stu.christs.cam.ac.uk/~aia21/ 106 D: Maintainer of ide-cd and Uniform CD-ROM driver, 107 D: ATAPI CD-Changer support, Major 2.1.x CD-ROM update. [all …]
|
D | Makefile | 1 # SPDX-License-Identifier: GPL-2.0 12 # expect to learn how to build the kernel reading this file. 14 ifeq ($(filter output-sync,$(.FEATURES)),) 25 # We are using a recursive build, so we need to do a little thinking 28 # Most importantly: sub-Makefiles should only ever modify files in 31 # unavoidable when linking the built-in.a targets which finally 41 this-makefile := $(lastword $(MAKEFILE_LIST)) 42 abs_srctree := $(realpath $(dir $(this-makefile))) 47 # Do not use make's built-in rules and variables 48 # (this increases performance and avoids hard-to-debug behaviour) [all …]
|
D | MAINTAINERS | 5 --------------------------------------------------- 21 W: *Web-page* with status/info 23 B: URI for where to file *bugs*. A web-page with detailed bug 28 patches to the given subsystem. This is either an in-tree file, 29 or a URI. See Documentation/maintainer/maintainer-entry-profile.rst 46 N: [^a-z]tegra all files whose path contains tegra 64 ---------------- 83 3WARE SAS/SATA-RAID SCSI DRIVERS (3W-XXXX, 3W-9XXX, 3W-SAS) 85 L: linux-scsi@vger.kernel.org 88 F: drivers/scsi/3w-* [all …]
|
/linux-6.15/Documentation/process/ |
D | embargoed-hardware-issues.rst | 7 ----- 23 ------- 31 Linux kernel security team (:ref:`Documentation/admin-guide/ 34 The team can be contacted by email at <hardware-security@kernel.org>. This 43 - PGP: https://www.kernel.org/static/files/hardware-security.asc 44 - S/MIME: https://www.kernel.org/static/files/hardware-security.crt 55 - Linus Torvalds (Linux Foundation Fellow) 56 - Greg Kroah-Hartman (Linux Foundation Fellow) 57 - Thomas Gleixner (Linux Foundation Fellow) 59 Operation of mailing-lists [all …]
|
D | handling-regressions.rst | 1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0) 7 *We don't cause regressions* -- this document describes what this "first rule of 9 Documentation/admin-guide/reporting-regressions.rst, which covers the topic from a 21 loop by immediately sending at least a brief "Reply-all" with the list 30 introduced: v5.13..v5.14-rc1``. If not, send a reply (with the regressions 39 #regzbot introduced: v5.13..v5.14-rc1 45 mandated by Documentation/process/submitting-patches.rst and 61 ----------------------------------- 72 it into the loop by sending at least a brief "Reply-all" with the list CCed; 79 Documentation/admin-guide/reporting-issues.rst. [all …]
|