| /linux/Documentation/process/ |
| H A 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 …]
|
| H A 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 …]
|
| H A D | stable-kernel-rules.rst | 45 1. Add a 'stable tag' to the description of a patch you then submit for
47 2. Ask the stable team to pick up a patch already mainlined.
48 3. Submit a patch to the stable team that is equivalent to a change already
56 options for cases where a mainlined patch needs adjustments to apply in older
70 To have a patch you submit for mainline inclusion later automatically picked up
79 Once the patch is mainlined it will be applied to the stable tree without
85 * Specify any additional patch prerequisites for cherry picking::
100 Note that for a patch series, you do not have to list as prerequisites the
102 patch series::
130 Cc: <stable@vger.kernel.org> # see patch description, needs adjustments for <= 6.3
[all …]
|
| H A 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
64 from happening. When you get review comments on a patch, take the time to
93 raised issues and how you dealt with them; the patch changelog is a good
114 If a patch is considered to be a good thing to add to the kernel, and once
128 patch. Now other developers working with that tree will get the patch by
134 What may also happen at this point, depending on the nature of your patch,
136 case, heavy patch conflicts can result in some work being put on the back
145 Some day, if all goes well, you'll log on and see that your patch has been
[all …]
|
| /linux/Documentation/translations/pt_BR/process/ |
| H A D | applying-patches.rst | 11 Este documento está obsoleto. Na maioria dos casos, em vez de usar ``patch``
15 an patch ao kernel ou, mais especificamente, a qual kernel base um patch para
24 O que é um Patch?
27 Um patch é um pequeno documento de texto que contém uma diferença (delta) de
31 Para aplicar um patch corretamente, você precisa saber de qual base ele foi
32 gerado e em qual nova versão o patch transformará a árvore de código-fonte.
33 Ambas as informações devem estar presentes nos metadados do arquivo de patch
37 Como eu aplico ou reverto um patch?
40 Você aplica um patch com o programa ``patch``. O programa patch lê um arquivo
41 de diff (ou patch) e faz as alterações descritas nele na árvore de
[all …]
|
| H A D | 5.Posting.rst | 58 resumo dos resultados deve ser incluído junto ao patch.
76 regra geral, um patch deve ser baseado no mainline atual encontrado na árvore
83 amplos. Dependendo da área do seu patch e do que está acontecendo em outros
84 lugares, basear um patch contra essas outras árvores pode exigir uma quantidade
87 Apenas as alterações mais simples devem ser formatadas como um único patch; tudo
100 - Cada alteração logicamente independente deve ser formatada como um patch separado.
104 patch deve fazer uma alteração específica que possa ser revisada por si só e
108 alterações no mesmo patch. Se um único patch corrige uma falha crítica de
112 - Cada patch deve resultar em um kernel que compile e funcione corretamente; se
122 tornou a pessoa mais popular na lista de discussão do kernel. Um único patch
[all …]
|
| H A D | backporting.rst | 27 Aplicando o patch a uma árvore
30 Às vezes, o patch que você está fazendo backport já existe como um commit do
32 ``git cherry-pick``. No entanto, se o patch vier de um e-mail, como costuma
37 sobre o patch ser aplicado perfeitamente à sua árvore de código-fonte. Na
39 editar o patch para fazê-lo ser aplicado.
42 o patch se aplique de forma limpa e *então* fazer o cherry-pick dele para a sua
46 quiser aplicar um patch que acabou de chegar na LKML a um kernel estável mais
50 Geralmente é melhor usar exatamente a mesma base a partir da qual o patch foi
52 não esteja muito longe da base original. O único problema ao aplicar o patch na
59 por sua vez, torna menos provável que o patch seja aplicado no lugar errado (o
[all …]
|
| /linux/Documentation/translations/it_IT/process/ |
| H A 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:
54 maggiori informazioni sulle serie di patch, vedere la sezione successiva).
63 - La vostra patch ha delle conseguenze in termini di prestazioni?
66 incluso nella patch.
77 Preparazione di una patch
[all …]
|
| H A 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 …]
|
| H A D | stable-kernel-rules.rst | 11 Regole sul tipo di patch che vengono o non vengono accettate nei sorgenti
14 - Questa patch o una equivalente deve esistere già nei sorgenti principali di
40 Procedura per sottomettere patch per i sorgenti -stable
44 Una patch di sicurezza non dovrebbe essere gestita (solamente) dal processo
50 1. Aggiungi un'etichetta 'stable' alla descrizione della patch al momento della
52 2. Chiedere alla squadra "stable" di prendere una patch già applicata sui
54 3. Sottomettere una patch alla squadra "stable" equivalente ad una modifica già
62 L':ref:`it_option_3` è un'alternativa ai due metodi precedenti quando la patch
79 Aggiungete la seguente etichetta nell'area delle firme per far sì che una patch
91 Una volta che la patch è stata inclusa, verrà applicata anche sui sorgenti
[all …]
|
| H A 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 …]
|
| H A D | 2.Process.rst | 39 patch di ogni rilascio. All'inizio di ogni ciclo di sviluppo, la
43 patch per un nuovo ciclo di sviluppo (e tutte le più importanti modifiche)
45 1000 modifiche ("patch" o "gruppo di modifiche") al giorno.
149 Il ciclo di vita di una patch
152 Le patch non passano direttamente dalla tastiera dello sviluppatori
154 per assicurare che ogni patch sia di buona qualità e desiderata nel
156 meno importanti, o, nel caso di patch ampie e controverse, va avanti per anni.
161 come una patch viene inserita nel kernel. Ciò che segue è un'introduzione
165 Una patch attraversa, generalmente, le seguenti fasi:
173 - Prima revisione. Le patch vengono pubblicate sulle liste di discussione
[all …]
|
| /linux/scripts/ |
| H A 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/Documentation/livepatch/ |
| H A 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 …]
|
| H A 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/scripts/coccinelle/api/ |
| H A D | string_choices.cocci | 6 virtual patch
10 @str_plural depends on patch@
21 @str_plural_r depends on !patch@
38 @str_up_down depends on patch disable neg_if_exp@
44 @str_up_down_r depends on !patch disable neg_if_exp@
57 @str_down_up depends on patch disable neg_if_exp@
63 @str_down_up_r depends on !patch disable neg_if_exp@
76 @str_true_false depends on patch disable neg_if_exp@
82 @str_true_false_r depends on !patch disable neg_if_exp@
95 @str_false_true depends on patch disable neg_if_exp@
[all …]
|
| /linux/kernel/livepatch/ |
| H A 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 …]
|
| /linux/tools/testing/selftests/livepatch/ |
| H A 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/Documentation/ABI/testing/ |
| H A 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/sound/drivers/opl3/ |
| H A D | opl3_synth.c | 214 * Patch management
229 * load a patch, obviously.
234 * name is the name string of the patch.
245 struct fm_patch *patch; in snd_opl3_load_patch() local
248 patch = snd_opl3_find_patch(opl3, prog, bank, 1); in snd_opl3_load_patch()
249 if (!patch) in snd_opl3_load_patch()
252 patch->type = type; in snd_opl3_load_patch()
255 patch->inst.op[i].am_vib = data[AM_VIB + i]; in snd_opl3_load_patch()
256 patch->inst.op[i].ksl_level = data[KSL_LEVEL + i]; in snd_opl3_load_patch()
257 patch->inst.op[i].attack_decay = data[ATTACK_DECAY + i]; in snd_opl3_load_patch()
[all …]
|
| /linux/scripts/livepatch/ |
| H A D | init.c | 12 static struct klp_patch *patch; variable
26 pr_err("nothing to patch!\n"); in livepatch_mod_init()
31 patch = kzalloc_obj(*patch); in livepatch_mod_init()
32 if (!patch) { in livepatch_mod_init()
70 patch->mod = THIS_MODULE; in livepatch_mod_init()
71 patch->objs = objs; in livepatch_mod_init()
73 /* TODO patch->states */ in livepatch_mod_init()
76 patch->replace = false; in livepatch_mod_init()
78 patch->replace = true; in livepatch_mod_init()
81 return klp_enable_patch(patch); in livepatch_mod_init()
[all …]
|
| H A D | klp-build | 34 FIX_PATCH_LINES="$SCRIPT_DIR/fix-patch-lines"
134 -o, --output=<file.ko> Output file [default: livepatch-<patch-name>.ko]
145 5|kmod Build patch module
160 local patch
241 for patch in "${PATCHES[@]}"; do
242 [[ -f "$patch" ]] || die "$patch doesn't exist"
295 # name based on the patch name.
303 NAME="patch"
312 # Hardcode the value printed by the localversion script to prevent patch
[all...] |
| /linux/arch/xtensa/kernel/ |
| H A D | jump_label.c | 26 struct patch { struct
41 struct patch *patch = data; in patch_text_stop_machine() local
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/sound/synth/emux/ |
| H A 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()
32 if (patch.type >= SNDRV_SFNT_LOAD_INFO && in snd_emux_hwdep_load_patch()
33 patch.type <= SNDRV_SFNT_PROBE_DATA) { in snd_emux_hwdep_load_patch()
35 patch.len + sizeof(patch), in snd_emux_hwdep_load_patch()
41 return emu->ops.load_fx(emu, patch.type, patch.optarg, arg, patch.len + sizeof(patch)); in snd_emux_hwdep_load_patch()
|
| H A D | soundfont.c | 64 * close the patch if the patch was opened by this client.
78 * Deal with a soundfont patch. Any driver could use these routines
90 struct soundfont_patch_info patch; in snd_soundfont_load() local
93 if (count < (long)sizeof(patch)) { in snd_soundfont_load()
94 dev_err(card->dev, "patch record too small %ld\n", count); in snd_soundfont_load()
97 if (copy_from_user(&patch, data, sizeof(patch))) in snd_soundfont_load()
100 count -= sizeof(patch); in snd_soundfont_load()
101 data += sizeof(patch); in snd_soundfont_load()
103 if (patch.key != SNDRV_OSS_SOUNDFONT_PATCH) { in snd_soundfont_load()
104 dev_err(card->dev, "The wrong kind of patch %x\n", patch.key); in snd_soundfont_load()
[all …]
|