Home
last modified time | relevance | path

Searched +full:fedora +full:- +full:release (Results 1 – 18 of 18) sorted by relevance

/linux-6.15/scripts/
Dsphinx-pre-install2 # SPDX-License-Identifier: GPL-2.0-or-later
5 # Copyright (c) 2017-2020 Mauro Carvalho Chehab <mchehab@kernel.org>
47 # List of required texlive packages on Fedora and OpenSuse
51 'amsfonts.sty' => 'texlive-amsfonts',
52 'amsmath.sty' => 'texlive-amsmath',
53 'amssymb.sty' => 'texlive-amsfonts',
54 'amsthm.sty' => 'texlive-amscls',
55 'anyfontsize.sty' => 'texlive-anyfontsize',
56 'atbegshi.sty' => 'texlive-oberdiek',
57 'bm.sty' => 'texlive-tools',
[all …]
Dld-version.sh2 # SPDX-License-Identifier: GPL-2.0
4 # Print the linker name and its version in a 5 or 6-digit form.
7 set -e
9 # Convert the version string x.y.z to a canonical 5 or 6-digit form.
13 set -- $1
19 echo $((10000 * $1 + 100 * ${2:-0} + ${3:-0}))
24 # Get the first line of the --version output.
27 set -- $(LC_ALL=C "$@" --version)
31 set -- $1
33 min_tool_version=$(dirname $0)/min-tool-version.sh
[all …]
/linux-6.15/drivers/gpu/drm/ci/
Dbuild.yml3 - .container+build-rules
4 stage: build-only
7 - artifacts
9 - FDO_CI_CONCURRENT=${FDO_CI_CONCURRENT} bash drivers/gpu/drm/ci/build.sh
13 - .build
14 - .use-debian/arm64_build
16 - aarch64
24 - .build
25 - .use-debian/arm64_build
27 - aarch64
[all …]
/linux-6.15/Documentation/admin-guide/nfs/
Dnfs-rdma.rst18 was first included in the following release, Linux 2.6.25.
29 nfs-rdma-devel@lists.sourceforge.net mailing list.
37 - Install an RDMA device
41 Testing has been performed using several Mellanox-based IB cards, the
44 - Install a Linux distribution and tools
46 The first kernel release to contain both the NFS/RDMA client and server was
48 Linux kernel release should be installed.
51 distributions from Red Hat's Fedora Project (http://fedora.redhat.com/).
53 - Install nfs-utils-1.1.2 or greater on the client
56 nfs-utils-1.1.2 or greater (nfs-utils-1.1.1 was the first nfs-utils
[all …]
/linux-6.15/tools/testing/selftests/rcutorture/doc/
Drcu-test-image.txt11 filled-out userspace, perhaps containing libraries, executables for
27 rcu-test-image file that contains the filesystem used by the guest-OS
34 ------------------------------------------------------------------------
35 dd if=/dev/zero of=rcu-test-image bs=400M count=1
36 mkfs.ext3 ./rcu-test-image
37 sudo mount -o loop ./rcu-test-image /mnt
39 # Replace "precise" below with your favorite Ubuntu release.
40 # Empirical evidence says this image will work for 64-bit, but...
42 sudo debootstrap --verbose --arch i386 precise /mnt http://archive.ubuntu.com/ubuntu
54 ------------------------------------------------------------------------
[all …]
/linux-6.15/tools/testing/ktest/examples/
Dkvm.conf24 # TESTS = patchcheck, randconfig, boot, test, config-bisect, bisect, min-config
52 # The example here assumes that Guest is running a Fedora release
56 POST_INSTALL = ${SSH} /sbin/dracut -f /boot/initramfs-test.img $KERNEL_VERSION
59 # the reboot command and then do a full power-cycle of the guest.
92 INCLUDE include/min-config.conf
Dvmware.conf5 # -------------
6 # - Edit the Virtual Machine ("Edit virtual machine settings")
7 # - Add a Serial Port
8 # - You almost certainly want it set "Connect at power on"
9 # - Select "Use socket (named pipe)"
10 # - Select a name that you'll recognize, like 'ktestserialpipe'
11 # - From: Server
12 # - To: A Virtual Machine
13 # - Save
14 # - Make sure you note the name, it will be in the base directory of the
[all …]
/linux-6.15/Documentation/rust/
Dquick-start.rst1 .. 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
45 apt install rustc rust-src bindgen rustfmt rust-clippy
48 Fedora Linux
51 Fedora Linux provides recent Rust releases and thus it should generally work out
54 dnf install rust rust-src bindgen-cli rustfmt clippy
63 USE='rust-src rustfmt clippy' emerge dev-lang/rust dev-util/bindgen
76 nativeBuildInputs = with pkgs; [ rustc rust-bindgen rustfmt clippy ];
[all …]
/linux-6.15/Documentation/networking/
Dnetconsole.rst1 .. SPDX-License-Identifier: GPL-2.0
16 Release prepend support by Breno Leitao <leitao@debian.org>, Jul 7 2023
31 It can be used either built-in or as a module. As a built-in,
43 netconsole=[+][r][src-port]@[src-ip]/[<dev>],[tgt-port]@<tgt-ip>/[tgt-macaddr]
47 r if present, prepend kernel version (release) to the message
48 src-port source for UDP packets (defaults to 6665)
49 src-ip source IP to use (interface address)
51 tgt-port port for logging agent (6666)
52 tgt-ip IP address for logging agent
53 tgt-macaddr ethernet MAC address for logging agent (broadcast)
[all …]
Dbonding.rst1 .. SPDX-License-Identifier: GPL-2.0
9 Initial release: Thomas Davis <tadavis at lbl.gov>
11 Corrections, HA extensions: 2000/10/03-15:
13 - Willy Tarreau <willy at meta-x.org>
14 - Constantine Gavrilov <const-g at xpert.com>
15 - Chad N. Tindel <ctindel at ieee dot org>
16 - Janice Girouard <girouard at us dot ibm dot com>
17 - Jay Vosburgh <fubar at us dot ibm dot com>
22 - Mitch Williams <mitch.a.williams at intel.com>
35 the original tools from extreme-linux and beowulf sites will not work
[all …]
/linux-6.15/Documentation/translations/zh_CN/doc-guide/
Dsphinx.rst1 .. include:: ../disclaimer-zh_CN.rst
3 :Original: Documentation/doc-guide/sphinx.rst
12 Linux内核使用 `Sphinx <http://www.sphinx-doc.org/>`_ 来把 ``Documentation``
17 reStructuredText文件可能包含包含来自源文件的结构化文档注释或kernel-doc注释。
18 通常它们用于描述代码的功能、类型和设计。kernel-doc注释有一些特殊的结构和
32 :ref:`sphinx-pre-install_zh` 。
38 ``virtualenv-3`` 或 ``virtualenv`` 在虚拟环境中安装Sphinx，具体取决于发行版
53 (sphinx_2.4.4) $ pip install -r Documentation/sphinx/requirements.txt
60 --------
69 --------------
[all …]
/linux-6.15/Documentation/admin-guide/
Dmodule-signing.rst2 ------------------------------
6 .. - Overview.
7 .. - Configuring module signing.
8 .. - Generating signing keys.
9 .. - Public keys in the kernel.
10 .. - Manually signing modules.
11 .. - Signed modules and stripping.
12 .. - Loading signed modules.
13 .. - Non-valid signatures and unsigned modules.
14 .. - Administering/protecting the private key.
[all …]
Dquickly-build-trimmed-linux.rst1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0)
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
26 git clone --depth 1 -b master \
34 make -j $(nproc --all)
37 command -v installkernel && sudo make modules_install install
43 git fetch --depth 1 origin
45 git checkout --force --detach origin/master
49 make -j $(nproc --all)
[all …]
Dreporting-issues.rst1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0)
15 you don't find any, install `the latest release from that series
30 supported stable or longterm series as well? Then install its latest release.
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
[all …]
Dverify-bugs-and-bisect-regressions.rst1 .. 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
49 will be considered the 'good' release and used to prepare the .config file.
55 # * Ensure Secure Boot permits booting self-compiled Linux kernels.
59 git clone -o mainline --no-checkout \
[all …]
/linux-6.15/Documentation/doc-guide/
Dsphinx.rst12 .. _Sphinx: http://www.sphinx-doc.org/
16 documentation comments, or kernel-doc comments, from source files. Usually these
18 kernel-doc comments have some special structure and formatting, but beyond that
34 :ref:`sphinx-pre-install` for further details.
42 Sphinx inside a virtual environment, using ``virtualenv-3``
56 (sphinx_latest) $ pip install -r Documentation/sphinx/requirements.txt
64 ------------
75 --------------------
86 ------------------------
95 The former was the only option for pre-6.1 kernel documentation and it
[all …]
/linux-6.15/Documentation/translations/it_IT/doc-guide/
Dsphinx.rst1 .. include:: ../disclaimer-ita.rst
4 :ref:`Documentation/doc-guide/index.rst <doc_guide>`
18 .. _Sphinx: http://www.sphinx-doc.org/
22 includere i commenti di documentazione, o di tipo kernel-doc, dai file
25 e l'architettura del codice. I commenti di tipo kernel-doc hanno una struttura
42 consultate :ref:`it_sphinx-pre-install`.
52 ``virtualenv-3`` o ``virtualenv`` a seconda di come Python 3 è stato
70 (sphinx_2.4.4) $ pip install -r Documentation/sphinx/requirements.txt
78 ----------------------
90 --------------------------
[all …]
/linux-6.15/Documentation/bpf/
Dbpf_devel_QA.rst10 Documentation/process/submitting-patches.rst. This document only describes
21 --------------------------------------------
48 ------------------------------------------------------------------------
49 A: BPF CI is GitHub based and hosted at https://github.com/kernel-patches/bpf.
55 - Create a fork of the aforementioned repository in your own account (one time
58 - Clone the fork locally, check out a new branch tracking either the bpf-next
59 or bpf branch, and apply your to-be-tested patches on top of it
61 - Push the local branch to your fork and create a pull request against
62 kernel-patches/bpf's bpf-next_base or bpf_base branch, respectively
68 Note furthermore that both base branches (bpf-next_base and bpf_base) will be
[all …]