Lines Matching refs:patches

19 In addition to explaining how to apply and revert patches, a brief
21 their specific patches) is also provided.
144 If you don't have any third-party patches applied to your kernel source, but
145 only patches from kernel.org and you apply the patches in the correct order,
157 in the wrong directory. Less often, you'll find patches that need to be
203 So if you get these errors with kernel.org patches then you should probably
216 generate a patch representing the differences between two patches and then
220 step. The -z flag to interdiff will even let you feed it patches in gzip or
232 downloading and applying of patches (https://www.selenic.com/ketchup/).
241 Where can I download the patches?
244 The patches are available at https://kernel.org/
245 Most recent patches are linked from the front page, but they also have
248 The 5.x.y (-stable) and 5.x patches live at
252 The 5.x.y incremental patches live at
256 The -rc patches are not stored on the webserver but are generated on
261 The stable -rc patches live at
278 that such patches do **NOT** apply on top of 5.x.y kernels but on top of the
315 The -stable team provides normal as well as incremental patches. Below is
316 how to apply these patches.
318 Normal patches
321 These patches are not incremental, meaning that for example the 5.7.3
337 Incremental patches
340 Incremental patches are different: instead of being applied on top
369 The -rc patches are not incremental, they apply to a base 5.x kernel, just
370 like the 5.x.y patches described above. The kernel version before the -rcN
377 Here are 3 examples of how to apply these patches::
403 The -mm patches and the linux-next tree
406 The -mm patches are experimental patches released by Andrew Morton.
408 In the past, -mm tree were used to also test subsystem patches, but this
411 tree. The Subsystem maintainers push their patches first to linux-next,
414 The -mm patches serve as a sort of proving ground for new features and other
415 experimental patches that aren't merged via a subsystem tree.
416 Once such patches has proved its worth in -mm for a while Andrew pushes
419 The linux-next tree is daily updated, and includes the -mm patches.
421 lot of debugging patches not appropriate for mainline etc., and is the most
424 These patches are not appropriate for use on systems that are supposed to be
427 even more so for -mm patches or using a Kernel from the linux-next tree).
429 Testing of -mm patches and linux-next is greatly appreciated since the whole
439 I hope you are now clear on how to apply the various patches and help testing