| /Linux-v6.1/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 | 48 Describe your problem. Whether your patch is a one-line bug fix or
77 The maintainer will thank you if you write your patch description in a
81 Solve only one problem per patch. If your description starts to get
82 long, that's a sign that you probably need to split up your patch.
85 When you submit or resubmit a patch or patch series, include the
86 complete patch description and justification for it. Don't just
87 say that this is version N of the patch (series). Don't expect the
88 subsystem maintainer to refer back to earlier patch versions or referenced
89 URLs to find the patch description and put that into the patch.
90 I.e., the patch (series) and its description should be self-contained.
[all …]
|
| D | 5.Posting.rst | 50 summary of the results should be included with the patch.
60 Patch preparation
68 general rule, a patch should be based on the current mainline as found in
75 on the area of your patch and what is going on elsewhere, basing a patch
79 Only the most simple changes should be formatted as a single patch;
85 - The patch series you post will almost certainly not be the series of
93 patch. These changes can be small ("add a field to this structure") or
95 conceptually small and amenable to a one-line description. Each patch
100 changes in the same patch. If a single patch fixes a critical security
105 - Each patch should yield a kernel which builds and runs properly; if your
[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-v6.1/Documentation/translations/it_IT/process/ |
| D | 5.Posting.rst | 15 e di procedure per la pubblicazione delle patch; seguirle renderà la vita
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
46 l'invio delle patch alla comunità di sviluppo. Queste cose includono:
56 - La vostra patch ha delle conseguenze in termini di prestazioni?
59 incluso nella patch.
70 Preparazione di una patch
73 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.
22 Per delle patch relative alle associazioni per Device Tree leggete
25 Questa documentazione assume che sappiate usare ``git`` per preparare le patch.
44 sorgenti e desiderano che le patch siano preparate basandosi su di essi.
66 singolarmente le patch dai sorgenti principali; quindi, includete tutte
87 I manutentori vi saranno grati se scrivete la descrizione della patch in un
91 Risolvete solo un problema per patch. Se la vostra descrizione inizia ad
92 essere lunga, potrebbe essere un segno che la vostra patch necessita d'essere
[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
45 Una patch di sicurezza non dovrebbe essere gestita (solamente) dal processo
57 Per far sì che una patch venga automaticamente inclusa nei sorgenti stabili,
64 nell'area dedicata alla firme. Una volta che la patch è stata inclusa, verrà
73 Dopo che la patch è stata inclusa nei sorgenti Linux, inviate una mail a
74 stable@vger.kernel.org includendo: il titolo della patch, l'identificativo
83 Inviata la patch, dopo aver verificato che rispetta le regole descritte in
86 del kernel nel quale vorreste vedere la patch.
[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
36 messaggio, sia per la patch che per qualsiasi altro messaggio. Il sito
40 I programmi di posta elettronica che vengono usati per inviare le patch per il
45 Non inviate patch con ``format=flowed``. Questo potrebbe introdurre
49 Questo può corrompere le patch.
52 testo. Le patch inviate per posta elettronica dovrebbero essere codificate in
[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
41 5) Controllate lo stile del codice della vostra patch secondo le direttive
43 Prima dell'invio della patch, usate il verificatore di stile
46 vostra patch.
55 8) La patch è stata accuratamente revisionata rispetto alle più importanti
74 12) La patch è stata verificata con le seguenti opzioni abilitate
80 13) La patch è stata compilata e verificata in esecuzione con, e senza,
83 14) Se la patch ha effetti sull'IO dei dischi, eccetera: allora dev'essere
[all …]
|
| D | 7.AdvancedTopics.rst | 44 La prima cosa da fare prima di usarlo per produrre patch che saranno
56 Utilizzare git per produrre patch da sottomettere via email può essere
73 essere creati con attenzione; integrate patch dai rami di sviluppo
79 o fatta sparire completamente dalla storia. Una serie di patch può essere
84 di patch pulite e con meno problemi.
88 perfetta. Riscrivere la storia riscriverà le patch contenute in quella
97 Dunque, una volta che il vostro insieme di patch è stato reso disponibile
99 questa regola, e si rifiuterà di pubblicare nuove patch che non risultino
101 patch che non condividono la stessa storia). È possibile ignorare questo
103 un ramo già pubblicato. Un esempio è linux-next dove le patch vengono
[all …]
|
| /Linux-v6.1/kernel/livepatch/ |
| D | core.c | 25 #include "patch.h"
70 * Note that the patch might still be needed before klp_module_going() in klp_find_object_module()
101 static struct klp_object *klp_find_object(struct klp_patch *patch, in klp_find_object() argument
106 klp_for_each_object(patch, obj) { in klp_find_object()
323 * /sys/kernel/livepatch/<patch>
324 * /sys/kernel/livepatch/<patch>/enabled
325 * /sys/kernel/livepatch/<patch>/transition
326 * /sys/kernel/livepatch/<patch>/force
327 * /sys/kernel/livepatch/<patch>/<object>
328 * /sys/kernel/livepatch/<patch>/<object>/patched
[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"
52 * We allow to patch also functions where RCU is not watching,
65 * The transition to the target patch state is complete. Clean up the data
93 * from this patch on the ops->func_stack. Otherwise, after in klp_complete_transition()
157 * patch state.
238 * Determine whether it's safe to transition the task to the target patch state
285 * Try to safely switch a task to the target patch state. If it's currently
307 * functions. If all goes well, switch the task to the target patch in klp_try_switch_task()
377 * Try to switch all remaining tasks to the target patch state by walking the
382 * If any tasks are still stuck in the initial patch state, schedule a retry.
[all …]
|
| /Linux-v6.1/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-v6.1/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 | 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
84 switch over. When a patch is enabled, livepatch enters into a
87 sequence occurs when a patch is disabled, except the tasks converge from
95 safe to patch tasks:
99 the task is patched. In most cases this will patch most or all of
128 Unless we can come up with another way to patch kthreads, architectures
132 The /sys/kernel/livepatch/<patch>/transition file shows whether a patch
133 is in transition. Only a single patch can be in transition at a given
[all …]
|
| /Linux-v6.1/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-v6.1/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-v6.1/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-v6.1/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) == num_online_cpus()) { 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, cpu_online_mask); in patch_text()
|
| /Linux-v6.1/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-v6.1/arch/parisc/kernel/ |
| D | patch.c | 3 * functions to patch RO kernel text during runtime
16 #include <asm/patch.h>
18 struct patch { struct
103 struct patch *patch = data; in patch_text_stop_machine() local
105 __patch_text_multiple(patch->addr, patch->insn, patch->len); in patch_text_stop_machine()
111 struct patch patch = { in patch_text() local
117 stop_machine_cpuslocked(patch_text_stop_machine, &patch, NULL); in patch_text()
123 struct patch patch = { in patch_text_multiple() local
129 stop_machine_cpuslocked(patch_text_stop_machine, &patch, NULL); in patch_text_multiple()
|
| /Linux-v6.1/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
227 * Verify the patch in @buf.
231 * positive: patch is not for this family, skip it
254 * Check if the remaining buffer is big enough to contain a patch of in verify_patch()
[all …]
|
