| /linux-6.12.1/Documentation/devicetree/bindings/usb/ |
| D | ti,tps6598x.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Texas Instruments 6598x Type-C Port Switch and Power Delivery controller
10 - Bryan O'Donoghue <bryan.odonoghue@linaro.org>
13 Texas Instruments 6598x Type-C Port Switch and Power Delivery controller
21 - ti,tps6598x
22 - apple,cd321x
23 - ti,tps25750
28 - description: main PD controller address
[all …]
|
| /linux-6.12.1/Documentation/hwmon/ |
| D | submitting-patches.rst | 1 How to Get Your Patch Accepted Into the Hwmon Subsystem
10 ----------
14 - Documentation/process/submit-checklist.rst
15 - Documentation/process/submitting-patches.rst
16 - Documentation/process/coding-style.rst
18 * Please run your patch through 'checkpatch --strict'. There should be no
22 * Please use the standard multi-line comment style. Do not mix C and C++
26 * If your patch generates checkpatch errors, warnings, or check messages,
32 * Please test your patch thoroughly. We are not your test group.
33 Sometimes a patch can not or not completely be tested because of missing
[all …]
|
| /linux-6.12.1/kernel/livepatch/ |
| D | transition.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * transition.c - Kernel Live Patching transition functions
5 * Copyright (C) 2015-2016 Josh Poimboeuf <jpoimboe@redhat.com>
14 #include "patch.h"
32 * cond_resched(). This helps CPU-bound kthreads get patched.
74 * We allow to patch also functions where RCU is not watching,
87 * The transition to the target patch state is complete. Clean up the data
98 klp_transition_patch->mod->name, in klp_complete_transition()
101 if (klp_transition_patch->replace && klp_target_state == KLP_TRANSITION_PATCHED) { in klp_complete_transition()
115 * from this patch on the ops->func_stack. Otherwise, after in klp_complete_transition()
[all …]
|
| D | core.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * core.c - Kernel Live Patching Core
25 #include "patch.h"
31 * accesses to klp-related variables and structures must have mutex protection,
34 * - klp_ftrace_handler()
35 * - klp_update_patch_state()
36 * - __klp_sched_try_switch()
51 return obj->name; in klp_is_module()
54 /* sets obj->mod if object is not vmlinux and module is found */
68 mod = find_module(obj->name); in klp_find_object_module()
[all …]
|
| /linux-6.12.1/Documentation/RCU/ |
| D | RTFP.txt | 4 This document describes RCU-related publications, and is followed by
19 with short-lived threads, such as the K42 research operating system.
20 However, Linux has long-lived tasks, so more is needed.
23 serialization, which is an RCU-like mechanism that relies on the presence
27 that these overheads were not so expensive in the mid-80s. Nonetheless,
28 passive serialization appears to be the first deferred-destruction
30 has lapsed, so this approach may be used in non-GPL software, if desired.
34 In 1987, Rashid et al. described lazy TLB-flush [RichardRashid87a].
36 this paper helped inspire the update-side batching used in the later
38 a description of Argus that noted that use of out-of-date values can
[all …]
|
| /linux-6.12.1/Documentation/livepatch/ |
| D | livepatch.rst | 30 - The kernel probes are the most generic. The code can be redirected by
33 - The function tracer calls the code from a predefined location that is
35 compiler using the '-pg' gcc option.
37 - Livepatching typically needs to redirect the code at the very beginning
46 a live patch is called with the help of a custom ftrace handler. But there are
64 But there are more complex fixes. For example, a patch might change
65 ordering of locking in multiple functions at the same time. Or a patch
74 The aim is to define a so-called consistency model. It attempts to define
79 kpatch: it uses kGraft's per-task consistency and syscall barrier
83 Patches are applied on a per-task basis, when the task is deemed safe to
[all …]
|
| D | module-elf-format.rst | 16 Formerly, livepatch required separate architecture-specific code to write
17 relocations. However, arch-specific code to write relocations already
19 code. So, instead of duplicating code and re-implementing what the module
21 loader to perform the all the arch-specific relocation work. Specifically,
23 write relocations. The patch module ELF format described in this document
26 of arch-specific code required to port livepatch to a particular
34 selected from OS-specific ranges according to the definitions from glibc.
37 -----------------------------------------------------
39 reference non-exported global symbols and non-included local symbols.
40 Relocations referencing these types of symbols cannot be left in as-is
[all …]
|
| /linux-6.12.1/drivers/scsi/aic7xxx/aicasm/ |
| D | aicasm.c | 19 * 3. Neither the names of the above-listed copyright holders nor the names
66 typedef struct patch { struct
67 STAILQ_ENTRY(patch) links;
74 STAILQ_HEAD(patch_list, patch) patches; argument
81 static void emit_patch(scope_t *scope, int patch);
134 sentinal->type = SCOPE_ROOT; in main()
146 while ((ch = getopt(argc, argv, "d:i:l:n:o:p:r:I:")) != -1) { in main()
157 fprintf(stderr, "%s: -d Requires either an " in main()
162 stop("-d: Assembler not built with debugging " in main()
178 /* Don't complain about the -nostdinc directrive */ in main()
[all …]
|
| /linux-6.12.1/Documentation/process/ |
| D | 5.Posting.rst | 13 :ref:`Documentation/process/submitting-patches.rst <submittingpatches>`
14 and :ref:`Documentation/process/submit-checklist.rst <submitchecklist>`.
18 ------------
24 consider posting in-progress work, or even making a git tree available so
30 patches which are known to be half-baked, but those who do will come in
35 -----------------------
40 - Test the code to the extent that you can. Make use of the kernel's
42 combinations of configuration options, use cross-compilers to build for
45 - Make sure your code is compliant with the kernel coding style
48 - Does your change have performance implications? If so, you should run
[all …]
|
| D | email-clients.rst | 7 ---
9 These days most developers use ``git send-email`` instead of regular
13 If you are new to ``git`` then send your first patch to yourself. Save it
16 the patch to the appropriate mailing list(s).
19 -------------------
23 attachments, but then the attachments should have content-type
25 it makes quoting portions of the patch more difficult in the patch
34 patch text untouched. For example, they should not modify or delete tabs
41 This can also corrupt your patch.
44 Emailed patches should be in ASCII or UTF-8 encoding only.
[all …]
|
| D | stable-kernel-rules.rst | 3 Everything you ever wanted to know about Linux -stable releases
7 "-stable" tree:
9 - It or an equivalent fix must already exist in Linux mainline (upstream).
10 - It must be obviously correct and tested.
11 - It cannot be bigger than 100 lines, with context.
12 - It must follow the
13 :ref:`Documentation/process/submitting-patches.rst <submittingpatches>`
15 - It must either fix a real bug that bothers people or just add a device ID.
18 - It fixes a problem like an oops, a hang, data corruption, a real security
21 - Serious issues as reported by a user of a distribution kernel may also
[all …]
|
| D | submitting-patches.rst | 13 works, see Documentation/process/development-process.rst. Also, read
14 Documentation/process/submit-checklist.rst
17 Documentation/devicetree/bindings/submitting-patches.rst.
20 If you're unfamiliar with ``git``, you would be well-advised to learn how to
26 :ref:`Documentation/process/maintainer-handbooks.rst <maintainer_handbooks_main>`.
29 ----------------------------
46 ---------------------
48 Describe your problem. Whether your patch is a one-line bug fix or
54 Describe user-visible impact. Straight up crashes and lockups are
59 vendor/product-specific trees that cherry-pick only specific patches
[all …]
|
| D | howto.rst | 6 This is the be-all, end-all document on this topic. It contains
18 ------------
27 The kernel is written mostly in C, with some architecture-dependent
30 you plan to do low-level development for that architecture. Though they
34 - "The C Programming Language" by Kernighan and Ritchie [Prentice Hall]
35 - "Practical C Programming" by Steve Oualline [O'Reilly]
36 - "C: A Reference Manual" by Harbison and Steele [Prentice Hall]
60 ------------
65 described in :ref:`Documentation/process/license-rules.rst <kernel_licensing>`.
72 https://www.gnu.org/licenses/gpl-faq.html
[all …]
|
| D | maintainer-netdev.rst | 1 .. SPDX-License-Identifier: GPL-2.0
3 .. _netdev-FAQ:
10 -----
12 - designate your patch to a tree - ``[PATCH net]`` or ``[PATCH net-next]``
13 - for fixes the ``Fixes:`` tag is required, regardless of the tree
14 - don't post large series (> 15 patches), break them up
15 - don't repost your patches within one 24h period
16 - reverse xmas tree
19 ------
21 netdev is a mailing list for all network-related Linux stuff. This
[all …]
|
| /linux-6.12.1/drivers/bluetooth/ |
| D | hci_ag6xx.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
41 return -ENOMEM; in ag6xx_open()
43 skb_queue_head_init(&ag6xx->txq); in ag6xx_open()
45 hu->priv = ag6xx; in ag6xx_open()
51 struct ag6xx_data *ag6xx = hu->priv; in ag6xx_close()
55 skb_queue_purge(&ag6xx->txq); in ag6xx_close()
56 kfree_skb(ag6xx->rx_skb); in ag6xx_close()
59 hu->priv = NULL; in ag6xx_close()
65 struct ag6xx_data *ag6xx = hu->priv; in ag6xx_flush()
69 skb_queue_purge(&ag6xx->txq); in ag6xx_flush()
[all …]
|
| D | btbcm.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
37 /* For kmalloc-ing the fw-name array instead of putting it on the stack */
51 return -EOPNOTSUPP; in btbcm_set_bdaddr_from_efi()
56 return -ENXIO; in btbcm_set_bdaddr_from_efi()
59 return -EIO; in btbcm_set_bdaddr_from_efi()
67 bt_dev_info(hdev, "BCM: Using EFI device address (%pMR)", &bdaddr); in btbcm_set_bdaddr_from_efi()
73 return -EOPNOTSUPP; in btbcm_set_bdaddr_from_efi()
87 bt_dev_err(hdev, "BCM: Reading device address failed (%d)", err); in btbcm_check_bdaddr()
91 if (skb->len != sizeof(*bda)) { in btbcm_check_bdaddr()
92 bt_dev_err(hdev, "BCM: Device address length mismatch"); in btbcm_check_bdaddr()
[all …]
|
| /linux-6.12.1/drivers/scsi/sym53c8xx_2/ |
| D | sym_fw.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
4 * of PCI-SCSI IO processors.
6 * Copyright (C) 1999-2001 Gerard Roudier <groudier@free.fr>
9 * Copyright (C) 1998-2000 Gerard Roudier
12 * a port of the FreeBSD ncr driver to Linux-1.2.13.
16 * Stefan Esser <se@mi.Uni-Koeln.de>
24 *-----------------------------------------------------------------------------
91 * Patch routine for firmware #1.
100 scripta0 = (struct sym_fw1a_scr *) np->scripta0; in sym_fw1_patch()
101 scriptb0 = (struct sym_fw1b_scr *) np->scriptb0; in sym_fw1_patch()
[all …]
|
| /linux-6.12.1/Documentation/translations/it_IT/process/ |
| D | 5.Posting.rst | 1 .. include:: ../disclaimer-ita.rst
15 e di procedure per la pubblicazione delle patch; seguirle renderà la vita
19 :ref:`translations/it_IT/process/submitting-patches.rst <it_submittingpatches>`
20 e :ref:`translations/it_IT/process/submit-checklist.rst <it_submitchecklist>`.
24 ------------------
26 C'è sempre una certa resistenza nel pubblicare patch finché non sono
27 veramente "pronte". Per semplici patch questo non è un problema.
37 Poche persone guarderanno delle patch che si sa essere fatte a metà,
42 Prima di creare patch
43 ---------------------
[all …]
|
| D | email-clients.rst | 1 .. include:: ../disclaimer-ita.rst
3 :Original: :doc:`../../../process/email-clients`
12 ---
14 Oggigiorno, la maggior parte degli sviluppatori utilizza ``git send-email``
17 per applicare le patch.
19 Se siete dei novelli utilizzatori di ``git`` allora inviate la patch a voi
21 il comando ``git am messaggio-formato-testo.txt`` e revisionatene il risultato
23 la patch alla lista di discussione più appropriata.
26 ------------------------
28 Le patch per il kernel vengono inviate per posta elettronica, preferibilmente
[all …]
|
| /linux-6.12.1/Documentation/filesystems/ |
| D | befs.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 implementation is neither complete nor well-tested.
28 Original Author: Makoto Kato <m_kato@ga2.so-net.ne.jp>
33 Does anyone know of a more current email address for Makoto? He doesn't
34 respond to the address given above...
41 for the linux 2.4.1 and later kernels. Currently it is a read-only
53 step 1. Install the BeFS patch into the source code tree of linux.
57 is called patch-befs-xxx, you would do the following:
60 patch -p1 < /path/to/patch-befs-xxx
68 The linux kernel has many compile-time options. Most of them are beyond the
[all …]
|
| /linux-6.12.1/arch/riscv/kernel/ |
| D | patch.c | 1 // SPDX-License-Identifier: GPL-2.0-only
16 #include <asm/patch.h>
39 * reg-a0) or BUILD_BUG_ON failed with "idx >= __end_of_fixed_addresses".
75 return -EINVAL; in __patch_insn_set()
121 return -EINVAL; in __patch_insn_write()
190 size = min(len, PAGE_SIZE * 2 - offset_in_page(addr)); in patch_insn_set()
196 len -= size; in patch_insn_set()
221 * Copy the instructions to the destination address, two pages at a time in patch_insn_write()
225 size = min(len, PAGE_SIZE * 2 - offset_in_page(addr)); in patch_insn_write()
232 len -= size; in patch_insn_write()
[all …]
|
| /linux-6.12.1/Documentation/networking/ |
| D | eql.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 Simon "Guru Aleph-Null" Janes, simon@ncm.com
12 that lets you load-balance IP serial links (SLIP or uncompressed PPP)
17 1.1.86. Some testing with 1.1.92 has been done with the v1.1 patch
18 which was only created to patch cleanly in the very latest kernel
27 together to work as one point-to-point link to increase your
32 The eql driver has only been tested with the Livingston PortMaster-2e
33 terminal server. I do not know if other terminal servers support load-
35 almost as well as the eql driver seems to do it (-- Unfortunately, in
36 my testing so far, the Livingston PortMaster 2e's load-balancing is a
[all …]
|
| /linux-6.12.1/Documentation/scsi/ |
| D | ChangeLog.lpfc | 2 * Please read the associated RELEASE-NOTES file !!!
8 * Fixed build warning for 2.6.12-rc2 kernels: mempool_alloc now
11 * Merged patch from Christoph Hellwig <hch@lst.de>: split helpers
19 * Removed FC_TRANSPORT_PATCHESxxx defines. They're in 2.6.12-rc1.
26 * Added PCI ID for LP10000-S.
31 * Zero-out response sense length in lpfc_scsi_prep_cmnd to prevent
33 - was causing spurious 0710 messages.
50 * Changed a few lines from patch submitted by Christoph Hellwig
53 * Merged patch from Christoph Hellwig (3/19): some misc patches
55 - stop using volatile. if you need special ordering use memory
[all …]
|
| /linux-6.12.1/Documentation/admin-guide/hw-vuln/ |
| D | srso.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 known scenario of poisoning CPU functional units - the Branch Target
9 Buffer (BTB) and Return Address Predictor (RAP) in this case - and then
13 AMD CPUs predict RET instructions using a Return Address Predictor (aka
14 Return Address Stack/Return Stack Buffer). In some cases, a non-architectural
20 but the concern is that an attacker can mis-train the CPU BTB to predict
21 non-architectural CALL instructions in kernel space and use this to
23 leading to information disclosure via a speculative side-channel.
25 The issue is tracked under CVE-2023-20569.
28 -------------------
[all …]
|
| /linux-6.12.1/arch/arm/mm/ |
| D | proc-v7m.S | 1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * linux/arch/arm/mm/proc-v7m.S
8 * This is the "shell" of the ARMv7-M processor support.
15 #include "proc-macros.S"
32 * - loc - location to jump to for soft reset
105 * This should be able to cover all ARMv7-M cores.
111 @ Configure the vector table base address
141 ldmia sp, {r0-r3, r12}
145 @ Special-purpose control register
151 stmiane sp, {r0-r6, lr} @ v7m_invalidate_l1 touches r0-r6
[all …]
|