| /linux-3.3/scripts/ |
| D | patch-kernel | 61 PNAME=patch-kernel
72 patch directory defaults to the current directory,
91 echo "cannot find patch file: ${patch}"
144 if $uncomp ${patchdir}/$1${ext} | patch -p1 -s -N -E -d $sourcedir
166 if $uncomp ${patchdir}/"$1"${ext} | patch -p1 -Rs -N -E -d $sourcedir
237 patch="patch-${CURRENTFULLVERSION}"
238 findFile $patchdir/${patch} || noFile ${patch}
239 reversePatch ${patch} || exit 1
267 patch=patch-$FULLVERSION
269 findFile $patchdir/${patch} || noFile ${patch}
[all …]
|
| /linux-3.3/Documentation/ |
| D | applying-patches.txt | 10 a patch to the kernel or, more specifically, what base kernel a patch for
19 What is a patch?
21 A patch is a small text document containing a delta of changes between two
24 To correctly apply a patch you need to know what base it was generated from
25 and what new version the patch will change the source tree into. These
26 should both be present in the patch file metadata or be possible to deduce
30 How do I apply or revert a patch?
32 You apply a patch with the `patch' program. The patch program reads a diff
33 (or patch) file and makes the changes to the source tree described in it.
38 This means that paths to files inside the patch file contain the name of the
[all …]
|
| D | SubmittingPatches | 31 generated by diff(1). When creating your patch, make sure to create it
38 To create a patch for a single file, it is often sufficient to do:
47 diff -up $SRCTREE/$MYFILE{.orig,} > /tmp/patch
49 To create a patch for multiple files, you should unpack a "vanilla",
58 linux-2.6.12-vanilla $MYSRC > /tmp/patch
62 patch. The "dontdiff" file is included in the kernel tree in
66 Make sure your patch does not include any extra files which do not
67 belong in a patch submission. Make sure to review your patch -after-
73 kernel developers, very important if you want your patch accepted.
79 Andrew Morton's patch scripts:
[all …]
|
| D | coccinelle.txt | 41 semantic patch code, but any results that are obtained should still be
51 Four modes are defined: patch, report, context, and org. The mode to
54 'patch' proposes a fix, when possible.
68 To make a report for every semantic patch, run the following command:
76 make coccicheck MODE=patch
79 The coccicheck target applies every semantic patch available in the
82 For each semantic patch, a commit message is proposed. It gives a
83 description of the problem being checked by the semantic patch, and
91 Using Coccinelle with a single semantic patch
95 semantic patch. In that case, the variable must be initialized with
[all …]
|
| D | stable_kernel_rules.txt | 26 - Send the patch, after verifying that it follows the above rules, to
30 - To have the patch automatically included in the stable tree, add the tag
32 in the sign-off area. Once the patch is merged it will be applied to
35 - If the patch requires other patches as prerequisites which can be
51 - The sender will receive an ACK when the patch has been accepted into the
52 queue, or a NAK if the patch is rejected. This response might take a few
54 - If accepted, the patch will be added to the -stable queue, for review by
64 the patch (unless the submitter is the maintainer of the area) and CC: to
66 - The review committee has 48 hours in which to ACK or NAK the patch.
67 - If the patch is rejected by a member of the committee, or linux-kernel
[all …]
|
| D | email-clients.txt | 10 it makes quoting portions of the patch more difficult in the patch
14 patch text untouched. For example, they should not modify or delete tabs
21 This can also corrupt your patch.
40 It's a good idea to send a patch to yourself, save the received message,
41 and successfully apply it with 'patch' before sending patches to Linux
64 When composing the message, the cursor should be placed where the patch
65 should appear, and then pressing CTRL-R let you specify the patch file
79 to insert the patch.
94 so you will have to manually word wrap text before the patch. The easiest
100 At the bottom of your email, put the commonly-used patch delimiter before
[all …]
|
| /linux-3.3/sound/drivers/opl3/ |
| D | opl3_synth.c | 257 struct fm_patch *patch; in snd_opl3_load_patch() local
260 patch = snd_opl3_find_patch(opl3, prog, bank, 1); in snd_opl3_load_patch()
261 if (!patch) in snd_opl3_load_patch()
264 patch->type = type; in snd_opl3_load_patch()
267 patch->inst.op[i].am_vib = data[AM_VIB + i]; in snd_opl3_load_patch()
268 patch->inst.op[i].ksl_level = data[KSL_LEVEL + i]; in snd_opl3_load_patch()
269 patch->inst.op[i].attack_decay = data[ATTACK_DECAY + i]; in snd_opl3_load_patch()
270 patch->inst.op[i].sustain_release = data[SUSTAIN_RELEASE + i]; in snd_opl3_load_patch()
271 patch->inst.op[i].wave_select = data[WAVE_SELECT + i]; in snd_opl3_load_patch()
273 patch->inst.feedback_connection[0] = data[CONNECTION]; in snd_opl3_load_patch()
[all …]
|
| /linux-3.3/sound/synth/emux/ |
| D | soundfont.c | 132 struct soundfont_patch_info patch; in snd_soundfont_load() local
136 if (count < (long)sizeof(patch)) { in snd_soundfont_load()
140 if (copy_from_user(&patch, data, sizeof(patch))) in snd_soundfont_load()
143 count -= sizeof(patch); in snd_soundfont_load()
144 data += sizeof(patch); in snd_soundfont_load()
146 if (patch.key != SNDRV_OSS_SOUNDFONT_PATCH) { in snd_soundfont_load()
147 snd_printk(KERN_ERR "The wrong kind of patch %x\n", patch.key); in snd_soundfont_load()
150 if (count < patch.len) { in snd_soundfont_load()
152 count, patch.len); in snd_soundfont_load()
155 if (patch.len < 0) { in snd_soundfont_load()
[all …]
|
| D | emux_hwdep.c | 37 struct soundfont_patch_info patch; in snd_emux_hwdep_load_patch() local
39 if (copy_from_user(&patch, arg, sizeof(patch))) in snd_emux_hwdep_load_patch()
42 if (patch.type >= SNDRV_SFNT_LOAD_INFO && in snd_emux_hwdep_load_patch()
43 patch.type <= SNDRV_SFNT_PROBE_DATA) { in snd_emux_hwdep_load_patch()
44 err = snd_soundfont_load(emu->sflist, arg, patch.len + sizeof(patch), TMP_CLIENT_ID); in snd_emux_hwdep_load_patch()
49 return emu->ops.load_fx(emu, patch.type, patch.optarg, arg, patch.len + sizeof(patch)); in snd_emux_hwdep_load_patch()
|
| /linux-3.3/arch/ia64/kernel/ |
| D | vmlinux.lds.S | 83 .data..patch.phys_stack_reg : AT(ADDR(.data..patch.phys_stack_reg) - LOAD_OFFSET) {
85 *(.data..patch.phys_stack_reg)
122 .data..patch.vtop : AT(ADDR(.data..patch.vtop) - LOAD_OFFSET) {
124 *(.data..patch.vtop)
128 .data..patch.rse : AT(ADDR(.data..patch.rse) - LOAD_OFFSET) {
130 *(.data..patch.rse)
134 .data..patch.mckinley_e9 : AT(ADDR(.data..patch.mckinley_e9) - LOAD_OFFSET) {
136 *(.data..patch.mckinley_e9)
|
| D | gate.lds.S | 36 .data..patch : {
38 *(.data..patch.mckinley_e9) argument
42 *(.data..patch.vtop) argument
46 *(.data..patch.fsyscall_table) argument
50 *(.data..patch.brl_fsys_bubble_down) argument
|
| /linux-3.3/Documentation/development-process/ |
| D | 5.Posting | 45 summary of the results should be included with the patch.
62 general rule, a patch should be based on the current mainline as found in
69 on the area of your patch and what is going on elsewhere, basing a patch
73 Only the most simple changes should be formatted as a single patch;
79 - The patch series you post will almost certainly not be the series of
87 patch. These changes can be small ("add a field to this structure") or
89 conceptually small and amenable to a one-line description. Each patch
94 changes in the same patch. If a single patch fixes a critical security
99 - Each patch should yield a kernel which builds and runs properly; if your
100 patch series is interrupted in the middle, the result should still be a
[all …]
|
| D | 6.Followthrough | 10 It is a rare patch which is so good at its first posting that there is no
21 A patch of any significance will result in a number of comments from other
27 - If you have explained your patch well, reviewers will understand its
53 from happening. When you get review comments on a patch, take the time to
82 raised issues and how you dealt with them; the patch changelog is a good
102 If a patch is considered to be a good thing to add to the kernel, and once
116 patch. Now other developers working with that tree will get the patch by
122 What may also happen at this point, depending on the nature of your patch,
124 case, heavy patch conflicts can result in some work being put on the back
133 Some day, if all goes well, you'll log on and see that your patch has been
[all …]
|
| /linux-3.3/sound/pci/hda/ |
| D | patch_si3054.c | 289 { .id = 0x163c3055, .name = "Si3054", .patch = patch_si3054 },
290 { .id = 0x163c3155, .name = "Si3054", .patch = patch_si3054 },
291 { .id = 0x11c13026, .name = "Si3054", .patch = patch_si3054 },
292 { .id = 0x11c13055, .name = "Si3054", .patch = patch_si3054 },
293 { .id = 0x11c13155, .name = "Si3054", .patch = patch_si3054 },
294 { .id = 0x10573055, .name = "Si3054", .patch = patch_si3054 },
295 { .id = 0x10573057, .name = "Si3054", .patch = patch_si3054 },
296 { .id = 0x10573155, .name = "Si3054", .patch = patch_si3054 },
298 { .id = 0x11063288, .name = "Si3054", .patch = patch_si3054 },
300 { .id = 0x15433155, .name = "Si3054", .patch = patch_si3054 },
[all …]
|
| D | patch_hdmi.c | 1872 { .id = 0x1002793c, .name = "RS600 HDMI", .patch = patch_atihdmi },
1873 { .id = 0x10027919, .name = "RS600 HDMI", .patch = patch_atihdmi },
1874 { .id = 0x1002791a, .name = "RS690/780 HDMI", .patch = patch_atihdmi },
1875 { .id = 0x1002aa01, .name = "R6xx HDMI", .patch = patch_generic_hdmi },
1876 { .id = 0x10951390, .name = "SiI1390 HDMI", .patch = patch_generic_hdmi },
1877 { .id = 0x10951392, .name = "SiI1392 HDMI", .patch = patch_generic_hdmi },
1878 { .id = 0x17e80047, .name = "Chrontel HDMI", .patch = patch_generic_hdmi },
1879 { .id = 0x10de0002, .name = "MCP77/78 HDMI", .patch = patch_nvhdmi_8ch_7x },
1880 { .id = 0x10de0003, .name = "MCP77/78 HDMI", .patch = patch_nvhdmi_8ch_7x },
1881 { .id = 0x10de0005, .name = "MCP77/78 HDMI", .patch = patch_nvhdmi_8ch_7x },
[all …]
|
| D | patch_sigmatel.c | 6404 { .id = 0x83847690, .name = "STAC9200", .patch = patch_stac9200 },
6405 { .id = 0x83847882, .name = "STAC9220 A1", .patch = patch_stac922x },
6406 { .id = 0x83847680, .name = "STAC9221 A1", .patch = patch_stac922x },
6407 { .id = 0x83847880, .name = "STAC9220 A2", .patch = patch_stac922x },
6408 { .id = 0x83847681, .name = "STAC9220D/9223D A2", .patch = patch_stac922x },
6409 { .id = 0x83847682, .name = "STAC9221 A2", .patch = patch_stac922x },
6410 { .id = 0x83847683, .name = "STAC9221D A2", .patch = patch_stac922x },
6411 { .id = 0x83847618, .name = "STAC9227", .patch = patch_stac927x },
6412 { .id = 0x83847619, .name = "STAC9227", .patch = patch_stac927x },
6413 { .id = 0x83847616, .name = "STAC9228", .patch = patch_stac927x },
[all …]
|
| /linux-3.3/scripts/coccinelle/api/ |
| D | resource_size.cocci | 17 virtual patch
25 @r_context depends on context && !patch && !org@
32 // For patch mode
35 @r_patch depends on !context && patch && !org@
47 @r_org depends on !context && !patch && (org || report)@
54 @rbad_org depends on !context && !patch && (org || report)@
|
| D | err_cast.cocci | 16 virtual patch
21 @ depends on context && !patch && !org && !report@
27 @ depends on !context && patch && !org && !report @
34 @r depends on !context && !patch && (org || report)@
|
| D | kstrdup.cocci | 11 virtual patch
16 @depends on patch@
29 @depends on patch@
46 @r1 depends on !patch exists@
59 @r2 depends on !patch exists@
|
| /linux-3.3/Documentation/zh_CN/ |
| D | SubmittingPatches | 61 diff -up $SRCTREE/$MYFILE{.orig,} > /tmp/patch
71 linux-2.6.12-vanilla $MYSRC > /tmp/patch
86 http://userweb.kernel.org/~akpm/stuff/patch-scripts.tar.gz
167 任何文件的作者/维护者对该文件的改动（例如 patch monkey 在重传模式下）
314 Subject: [patch 2/5] ext2: improve scalability of bitmap searching
396 Andrew Morton, "The perfect patch" (tpp).
399 Jeff Garzik, "Linux kernel patch submission format".
400 <http://linux.yyz.us/patch-format.html>
408 NO!!!! No more huge patch bombs to linux-kernel@vger.kernel.org people!
414 Linus Torvalds's mail on the canonical patch format:
|
| /linux-3.3/scripts/coccinelle/iterators/ |
| D | fen.cocci | 12 virtual patch
17 @depends on patch@
30 @depends on patch@
43 @depends on patch@
56 @depends on patch@
71 @r depends on !patch forall@
|
| /linux-3.3/arch/x86/kernel/ |
| D | microcode_amd.c | 79 void *patch; variable
187 memset(patch, 0, PAGE_SIZE); in get_matching_microcode()
190 get_ucode_data(patch, ucode_ptr + SECTION_HDR_SIZE, actual_size); in get_matching_microcode()
286 mc_hdr = patch; in generic_load_microcode()
287 new_mc = patch; in generic_load_microcode()
383 patch = (void *)get_zeroed_page(GFP_KERNEL); in init_amd_microcode()
384 if (!patch) in init_amd_microcode()
392 free_page((unsigned long)patch); in exit_amd_microcode()
|
| /linux-3.3/scripts/coccinelle/locks/ |
| D | call_kern.cocci | 14 virtual patch
73 @depends on locked && patch@
80 @depends on locked && !patch@
86 @script:python depends on !patch && org@
97 @script:python depends on !patch && report@
|
| /linux-3.3/Documentation/ja_JP/ |
| D | SubmittingPatches | 68 diff -up $SRCTREE/$MYFILE{.orig,} > /tmp/patch
79 linux-2.6.12-vanilla $MYSRC > /tmp/patch
101 Andrew Morton's patch scripts:
102 http://userweb.kernel.org/~akpm/stuff/patch-scripts.tar.gz
230 ・作者やメンテナによる修正(すなわち patch monkey の再転送モード)
538 Subject: [patch 2/5] ext2: improve scalability of bitmap searching
697 Andrew Morton, "The perfect patch" (tpp).
700 Jeff Garzik, "Linux kernel patch submission format".
701 <http://linux.yyz.us/patch-format.html>
709 NO!!!! No more huge patch bombs to linux-kernel@vger.kernel.org people!
[all …]
|
| /linux-3.3/scripts/coccinelle/api/alloc/ |
| D | drop_kmalloc_cast.cocci | 17 virtual patch
33 // For patch mode
36 @depends on patch@
|