| /Linux-v5.10/Documentation/process/ |
| D | applying-patches.rst | 11 This document is obsolete. In most cases, rather than using ``patch``
15 a patch to the kernel or, more specifically, what base kernel a patch for
24 What is a patch?
27 A patch is a small text document containing a delta of changes between two
31 To correctly apply a patch you need to know what base it was generated from
32 and what new version the patch will change the source tree into. These
33 should both be present in the patch file metadata or be possible to deduce
37 How do I apply or revert a patch?
40 You apply a patch with the ``patch`` program. The patch program reads a diff
41 (or patch) file and makes the changes to the source tree described in it.
[all …]
|
| D | submitting-patches.rst | 43 Describe your problem. Whether your patch is a one-line bug fix or
72 The maintainer will thank you if you write your patch description in a
76 Solve only one problem per patch. If your description starts to get
77 long, that's a sign that you probably need to split up your patch.
80 When you submit or resubmit a patch or patch series, include the
81 complete patch description and justification for it. Don't just
82 say that this is version N of the patch (series). Don't expect the
83 subsystem maintainer to refer back to earlier patch versions or referenced
84 URLs to find the patch description and put that into the patch.
85 I.e., the patch (series) and its description should be self-contained.
[all …]
|
| D | 5.Posting.rst | 51 summary of the results should be included with the patch.
61 Patch preparation
69 general rule, a patch should be based on the current mainline as found in
76 on the area of your patch and what is going on elsewhere, basing a patch
80 Only the most simple changes should be formatted as a single patch;
86 - The patch series you post will almost certainly not be the series of
94 patch. These changes can be small ("add a field to this structure") or
96 conceptually small and amenable to a one-line description. Each patch
101 changes in the same patch. If a single patch fixes a critical security
106 - Each patch should yield a kernel which builds and runs properly; if your
[all …]
|
| D | stable-kernel-rules.rst | 38 - If the patch covers files in net/ or drivers/net please follow netdev stable
43 to ensure the requested patch is not already queued up.
56 To have the patch automatically included in the stable tree, add the tag
62 in the sign-off area. Once the patch is merged it will be applied to
71 After the patch has been merged to Linus' tree, send an email to
72 stable@vger.kernel.org containing the subject of the patch, the commit ID,
81 Send the patch, after verifying that it follows the above rules, to
87 :ref:`option_2` and :ref:`option_3` are more useful if the patch isn't deemed
90 useful if the patch needs some special handling to apply to an older kernel
93 Note that for :ref:`option_3`, if the patch deviates from the original
[all …]
|
| D | 6.Followthrough.rst | 13 It is a rare patch which is so good at its first posting that there is no
25 A patch of any significance will result in a number of comments from other
31 - If you have explained your patch well, reviewers will understand its
57 from happening. When you get review comments on a patch, take the time to
86 raised issues and how you dealt with them; the patch changelog is a good
107 If a patch is considered to be a good thing to add to the kernel, and once
121 patch. Now other developers working with that tree will get the patch by
127 What may also happen at this point, depending on the nature of your patch,
129 case, heavy patch conflicts can result in some work being put on the back
138 Some day, if all goes well, you'll log on and see that your patch has been
[all …]
|
| /Linux-v5.10/Documentation/translations/it_IT/process/ |
| D | 5.Posting.rst | 15 e di procedure per la pubblicazione delle patch; seguirle renderà la vita
27 C'è sempre una certa resistenza nel pubblicare patch finché non sono
28 veramente "pronte". Per semplici patch questo non è un problema.
38 Poche persone guarderanno delle patch che si sa essere fatte a metà,
43 Prima di creare patch
47 l'invio delle patch alla comunità di sviluppo. Queste cose includono:
57 - La vostra patch ha delle conseguenze in termini di prestazioni?
60 incluso nella patch.
71 Preparazione di una patch
74 La preparazione delle patch per la pubblicazione può richiedere una quantità
[all …]
|
| D | submitting-patches.rst | 8 Inviare patch: la guida essenziale per vedere il vostro codice nel kernel
11 Una persona o un'azienda che volesse inviare una patch al kernel potrebbe
15 vostre patch accettate.
23 per delle patch relative alle associazioni per Device Tree leggete
28 patch molto del lavoro più ripetitivo lo troverete già fatto per voi, tuttavia
29 dovete preparare e documentare un certo numero di patch. Generalmente, l'uso
43 sorgenti e desiderano che le patch siano preparate basandosi su di essi.
55 Se dovete produrre le vostre patch a mano, usate ``diff -up`` o ``diff -uprN``
56 per crearle. Git produce di base le patch in questo formato; se state
59 Tutte le modifiche al kernel Linux avvengono mediate patch, come descritte
[all …]
|
| D | email-clients.rst | 17 per applicare le patch.
19 Se siete dei novelli utilizzatori di ``git`` allora inviate la patch a voi
23 la patch alla lista di discussione più appropriata.
28 Le patch per il kernel vengono inviate per posta elettronica, preferibilmente
32 ben apprezzati perché rende più difficile citare porzioni di patch durante il
35 I programmi di posta elettronica che vengono usati per inviare le patch per il
40 Non inviate patch con ``format=flowed``. Questo potrebbe introdurre
44 Questo può corrompere le patch.
47 testo. Le patch inviate per posta elettronica dovrebbero essere codificate in
55 Di solito, il copia-e-incolla (o taglia-e-incolla) non funziona con le patch
[all …]
|
| D | stable-kernel-rules.rst | 11 Regole sul tipo di patch che vengono o non vengono accettate nei sorgenti
37 - Questa patch o una equivalente deve esistere già nei sorgenti principali di
41 Procedura per sottomettere patch per i sorgenti -stable
44 - Se la patch contiene modifiche a dei file nelle cartelle net/ o drivers/net,
47 ma solo dopo aver verificato al seguente indirizzo che la patch non sia
50 - Una patch di sicurezza non dovrebbero essere gestite (solamente) dal processo
63 Per far sì che una patch venga automaticamente inclusa nei sorgenti stabili,
70 nell'area dedicata alla firme. Una volta che la patch è stata inclusa, verrà
79 Dopo che la patch è stata inclusa nei sorgenti Linux, inviate una mail a
80 stable@vger.kernel.org includendo: il titolo della patch, l'identificativo
[all …]
|
| D | 2.Process.rst | 42 patch di ogni rilascio. All'inizio di ogni ciclo di sviluppo, la
46 patch per un nuovo ciclo di sviluppo (e tutte le più importanti modifiche)
48 1000 modifiche ("patch" o "gruppo di modifiche") al giorno.
157 Il ciclo di vita di una patch
160 Le patch non passano direttamente dalla tastiera dello sviluppatori
162 per assicurare che ogni patch sia di buona qualità e desiderata nel
164 meno importanti, o, nel caso di patch ampie e controverse, va avanti per anni.
169 come una patch viene inserita nel kernel. Ciò che segue è un'introduzione
173 Una patch attraversa, generalmente, le seguenti fasi:
181 - Prima revisione. Le patch vengono pubblicate sulle liste di discussione
[all …]
|
| D | submit-checklist.rst | 8 Lista delle verifiche da fare prima di inviare una patch per il kernel Linux
12 vedere le proprie patch accettate più rapidamente.
15 sottomissione delle patch, in particolare
37 5) Controllate lo stile del codice della vostra patch secondo le direttive
39 Prima dell'invio della patch, usate il verificatore di stile
42 vostra patch.
51 8) La patch è stata accuratamente revisionata rispetto alle più importanti
71 12) La patch è stata verificata con le seguenti opzioni abilitate
77 13) La patch è stata compilata e verificata in esecuzione con, e senza,
80 14) Se la patch ha effetti sull'IO dei dischi, eccetera: allora dev'essere
[all …]
|
| /Linux-v5.10/kernel/livepatch/ |
| D | core.c | 24 #include "patch.h"
69 * Note that the patch might still be needed before klp_module_going() in klp_find_object_module()
100 static struct klp_object *klp_find_object(struct klp_patch *patch, in klp_find_object() argument
105 klp_for_each_object(patch, obj) { in klp_find_object()
324 * /sys/kernel/livepatch/<patch>
325 * /sys/kernel/livepatch/<patch>/enabled
326 * /sys/kernel/livepatch/<patch>/transition
327 * /sys/kernel/livepatch/<patch>/force
328 * /sys/kernel/livepatch/<patch>/<object>
329 * /sys/kernel/livepatch/<patch>/<object>/<function,sympos>
[all …]
|
| D | state.c | 15 #define klp_for_each_state(patch, state) \ argument
16 for (state = patch->states; state && state->id; state++)
20 * the given patch
21 * @patch: livepatch that modifies the given system state
24 * Checks whether the given patch modifies the given system state.
26 * The function can be called either from pre/post (un)patch
31 struct klp_state *klp_get_state(struct klp_patch *patch, unsigned long id) in klp_get_state() argument
35 klp_for_each_state(patch, state) { in klp_get_state()
58 * It is typically called only from pre/post (un)patch
66 struct klp_patch *patch; in klp_get_prev_state() local
[all …]
|
| D | transition.c | 13 #include "patch.h"
53 * We allow to patch also functions where RCU is not watching,
66 * The transition to the target patch state is complete. Clean up the data
94 * from this patch on the ops->func_stack. Otherwise, after in klp_complete_transition()
158 * patch state.
239 * Determine whether it's safe to transition the task to the target patch state
277 * Try to safely switch a task to the target patch state. If it's currently
304 * functions. If all goes well, switch the task to the target patch in klp_try_switch_task()
381 * Try to switch all remaining tasks to the target patch state by walking the
386 * If any tasks are still stuck in the initial patch state, schedule a retry.
[all …]
|
| /Linux-v5.10/scripts/ |
| D | patch-kernel | 4 # usage: patch-kernel [ sourcedir [ patchdir [ stopversion ] [ -acxx ] ] ]
5 # The source directory defaults to /usr/src/linux, and the patch
8 # scripts/patch-kernel . ..
11 # scripts/patch-kernel . .. -ac
12 # Get the latest Linux kernel and patch it with the latest ac patch
13 # scripts/patch-kernel . .. 2.4.9
15 # scripts/patch-kernel . .. 2.4.9 -ac
17 # scripts/patch-kernel . .. 2.4.9 -ac11
18 # Gets 2.4.9 with ac patch ac11
23 # It then looks for patches for the next sublevel in the patch directory.
[all …]
|
| /Linux-v5.10/Documentation/livepatch/ |
| D | callbacks.rst | 5 Livepatch (un)patch-callbacks provide a mechanism for livepatch modules
16 In most cases, (un)patch callbacks will need to be used in conjunction
26 patch.
39 * Pre-patch
42 * Post-patch
48 active), used to clean up post-patch callback
54 used to cleanup pre-patch callback resources
61 symmetry: pre-patch callbacks have a post-unpatch counterpart and
62 post-patch callbacks have a pre-unpatch counterpart. An unpatch
63 callback will only be executed if its corresponding patch callback was
[all …]
|
| D | livepatch.rst | 59 a live patch is called with the help of a custom ftrace handler. But there are
77 But there are more complex fixes. For example, a patch might change
78 ordering of locking in multiple functions at the same time. Or a patch
97 switch over. When a patch is enabled, livepatch enters into a
100 sequence occurs when a patch is disabled, except the tasks converge from
108 safe to patch tasks:
112 the task is patched. In most cases this will patch most or all of
141 Unless we can come up with another way to patch kthreads, architectures
145 The /sys/kernel/livepatch/<patch>/transition file shows whether a patch
146 is in transition. Only a single patch can be in transition at a given
[all …]
|
| /Linux-v5.10/tools/testing/selftests/livepatch/ |
| D | test-callbacks.sh | 20 # pre-patch callbacks are executed for vmlinux and $MOD_TARGET (those
22 # according to the klp_patch, their post-patch callbacks run and the
25 # - Similarly, on livepatch disable, pre-patch callbacks run before the
26 # unpatching transition starts. klp_objects are reverted, post-patch
40 livepatch: enabling patch '$MOD_LIVEPATCH'
67 # - On livepatch enable, only pre/post-patch callbacks are executed for
71 # pre/post-patch callbacks are executed.
85 livepatch: enabling patch '$MOD_LIVEPATCH'
93 livepatch: applying patch '$MOD_LIVEPATCH' to loading module '$MOD_TARGET'
135 livepatch: enabling patch '$MOD_LIVEPATCH'
[all …]
|
| /Linux-v5.10/sound/drivers/opl3/ |
| D | opl3_synth.c | 216 * Patch management
231 * load a patch, obviously.
236 * name is the name string of the patch.
247 struct fm_patch *patch; in snd_opl3_load_patch() local
250 patch = snd_opl3_find_patch(opl3, prog, bank, 1); in snd_opl3_load_patch()
251 if (!patch) in snd_opl3_load_patch()
254 patch->type = type; in snd_opl3_load_patch()
257 patch->inst.op[i].am_vib = data[AM_VIB + i]; in snd_opl3_load_patch()
258 patch->inst.op[i].ksl_level = data[KSL_LEVEL + i]; in snd_opl3_load_patch()
259 patch->inst.op[i].attack_decay = data[ATTACK_DECAY + i]; in snd_opl3_load_patch()
[all …]
|
| /Linux-v5.10/arch/xtensa/kernel/ |
| D | jump_label.c | 26 struct patch { struct
41 struct patch *patch = data; in patch_text_stop_machine() argument
43 if (atomic_inc_return(&patch->cpu_count) == 1) { in patch_text_stop_machine()
44 local_patch_text(patch->addr, patch->data, patch->sz); in patch_text_stop_machine()
45 atomic_inc(&patch->cpu_count); in patch_text_stop_machine()
47 while (atomic_read(&patch->cpu_count) <= num_online_cpus()) in patch_text_stop_machine()
49 __invalidate_icache_range(patch->addr, patch->sz); in patch_text_stop_machine()
57 struct patch patch = { in patch_text() local
64 &patch, NULL); in patch_text()
|
| /Linux-v5.10/Documentation/ABI/testing/ |
| D | sysfs-kernel-livepatch | 9 each loaded live patch module.
11 What: /sys/kernel/livepatch/<patch>
16 The patch directory contains subdirectories for each kernel
19 What: /sys/kernel/livepatch/<patch>/enabled
25 code is currently applied. Writing 0 will disable the patch
26 while writing 1 will re-enable the patch.
28 What: /sys/kernel/livepatch/<patch>/transition
33 An attribute which indicates whether the patch is currently in
36 What: /sys/kernel/livepatch/<patch>/force
45 use this feature without a clearance from a patch
[all …]
|
| /Linux-v5.10/sound/synth/emux/ |
| D | emux_hwdep.c | 17 * load patch
23 struct soundfont_patch_info patch; in snd_emux_hwdep_load_patch() local
25 if (copy_from_user(&patch, arg, sizeof(patch))) in snd_emux_hwdep_load_patch()
28 if (patch.key == GUS_PATCH) in snd_emux_hwdep_load_patch()
30 patch.len + sizeof(patch), in snd_emux_hwdep_load_patch()
33 if (patch.type >= SNDRV_SFNT_LOAD_INFO && in snd_emux_hwdep_load_patch()
34 patch.type <= SNDRV_SFNT_PROBE_DATA) { in snd_emux_hwdep_load_patch()
35 err = snd_soundfont_load(emu->sflist, arg, patch.len + sizeof(patch), TMP_CLIENT_ID); in snd_emux_hwdep_load_patch()
40 return emu->ops.load_fx(emu, patch.type, patch.optarg, arg, patch.len + sizeof(patch)); in snd_emux_hwdep_load_patch()
|
| D | soundfont.c | 91 * close the patch if the patch was opened by this client.
108 * Deal with a soundfont patch. Any driver could use these routines
119 struct soundfont_patch_info patch; in snd_soundfont_load() local
123 if (count < (long)sizeof(patch)) { in snd_soundfont_load()
124 snd_printk(KERN_ERR "patch record too small %ld\n", count); in snd_soundfont_load()
127 if (copy_from_user(&patch, data, sizeof(patch))) in snd_soundfont_load()
130 count -= sizeof(patch); in snd_soundfont_load()
131 data += sizeof(patch); in snd_soundfont_load()
133 if (patch.key != SNDRV_OSS_SOUNDFONT_PATCH) { in snd_soundfont_load()
134 snd_printk(KERN_ERR "The wrong kind of patch %x\n", patch.key); in snd_soundfont_load()
[all …]
|
| /Linux-v5.10/arch/parisc/kernel/ |
| D | patch.c | 3 * functions to patch RO kernel text during runtime
16 #include <asm/patch.h>
18 struct patch { struct
106 struct patch *patch = data; in patch_text_stop_machine() local
108 __patch_text_multiple(patch->addr, patch->insn, patch->len); in patch_text_stop_machine()
114 struct patch patch = { in patch_text() local
120 stop_machine_cpuslocked(patch_text_stop_machine, &patch, NULL); in patch_text()
126 struct patch patch = { in patch_text_multiple() local
132 stop_machine_cpuslocked(patch_text_stop_machine, &patch, NULL); in patch_text_multiple()
|
| /Linux-v5.10/arch/x86/kernel/cpu/microcode/ |
| D | amd.c | 47 * microcode patch we found to match.
61 * Microcode patch container file is prepended to the initrd in cpio
148 * Check whether there is a valid, non-truncated microcode patch section at the
152 * On success, @sh_psize returns the patch size according to the section header,
163 pr_debug("Truncated patch section.\n"); in __verify_patch_section()
182 pr_debug("Patch of size %u too short.\n", p_size); in __verify_patch_section()
194 * a patch of the indicated @sh_psize (and also whether this size does not
228 * Verify the patch in @buf.
232 * positive: patch is not for this family, skip it
255 * Check if the remaining buffer is big enough to contain a patch of in verify_patch()
[all …]
|
