Documentation/process/applying-patches.rst

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 -rc patches are not stored on the webserver but are generated on
257 The stable -rc patches live at
274 that such patches do **NOT** apply on top of 5.x.y kernels but on top of the
313  The -stable team usually do make incremental patches available as well
314  as patches against the latest mainline release, but I only cover the
318 These patches are not incremental, meaning that for example the 5.7.3
351 The -rc patches are not incremental, they apply to a base 5.x kernel, just
352 like the 5.x.y patches described above. The kernel version before the -rcN
359 Here are 3 examples of how to apply these patches::
385 The -mm patches and the linux-next tree
388 The -mm patches are experimental patches released by Andrew Morton.
390 In the past, -mm tree were used to also test subsystem patches, but this
393 tree. The Subsystem maintainers push their patches first to linux-next,
396 The -mm patches serve as a sort of proving ground for new features and other
397 experimental patches that aren't merged via a subsystem tree.
398 Once such patches has proved its worth in -mm for a while Andrew pushes
401 The linux-next tree is daily updated, and includes the -mm patches.
403 lot of debugging patches not appropriate for mainline etc., and is the most
406 These patches are not appropriate for use on systems that are supposed to be
409 even more so for -mm patches or using a Kernel from the linux-next tree).
411 Testing of -mm patches and linux-next is greatly appreciated since the whole
421 I hope you are now clear on how to apply the various patches and help testing