tjh.dev / kernel
Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux
fork atom

Merge branch 'docs-5.0-fix' into docs-next

Pick up Arnd's fix here as well.

Jonathan Corbet 8a3680e2 32c8966e

+78 -73
+16 -16
Documentation/admin-guide/README.rst
··· 1 1 .. _readme: 2 2 3 - Linux kernel release 4.x <http://kernel.org/> 3 + Linux kernel release 5.x <http://kernel.org/> 4 4 ============================================= 5 5 6 - These are the release notes for Linux version 4. Read them carefully, 6 + These are the release notes for Linux version 5. Read them carefully, 7 7 as they tell you what this is all about, explain how to install the 8 8 kernel, and what to do if something goes wrong. 9 9 ··· 63 63 directory where you have permissions (e.g. your home directory) and 64 64 unpack it:: 65 65 66 - xz -cd linux-4.X.tar.xz | tar xvf - 66 + xz -cd linux-5.x.tar.xz | tar xvf - 67 67 68 68 Replace "X" with the version number of the latest kernel. 69 69 ··· 72 72 files. They should match the library, and not get messed up by 73 73 whatever the kernel-du-jour happens to be. 74 74 75 - - You can also upgrade between 4.x releases by patching. Patches are 75 + - You can also upgrade between 5.x releases by patching. Patches are 76 76 distributed in the xz format. To install by patching, get all the 77 77 newer patch files, enter the top level directory of the kernel source 78 - (linux-4.X) and execute:: 78 + (linux-5.x) and execute:: 79 79 80 - xz -cd ../patch-4.x.xz | patch -p1 80 + xz -cd ../patch-5.x.xz | patch -p1 81 81 82 - Replace "x" for all versions bigger than the version "X" of your current 82 + Replace "x" for all versions bigger than the version "x" of your current 83 83 source tree, **in_order**, and you should be ok. You may want to remove 84 84 the backup files (some-file-name~ or some-file-name.orig), and make sure 85 85 that there are no failed patches (some-file-name# or some-file-name.rej). 86 86 If there are, either you or I have made a mistake. 87 87 88 - Unlike patches for the 4.x kernels, patches for the 4.x.y kernels 88 + Unlike patches for the 5.x kernels, patches for the 5.x.y kernels 89 89 (also known as the -stable kernels) are not incremental but instead apply 90 - directly to the base 4.x kernel. For example, if your base kernel is 4.0 91 - and you want to apply the 4.0.3 patch, you must not first apply the 4.0.1 92 - and 4.0.2 patches. Similarly, if you are running kernel version 4.0.2 and 93 - want to jump to 4.0.3, you must first reverse the 4.0.2 patch (that is, 94 - patch -R) **before** applying the 4.0.3 patch. You can read more on this in 90 + directly to the base 5.x kernel. For example, if your base kernel is 5.0 91 + and you want to apply the 5.0.3 patch, you must not first apply the 5.0.1 92 + and 5.0.2 patches. Similarly, if you are running kernel version 5.0.2 and 93 + want to jump to 5.0.3, you must first reverse the 5.0.2 patch (that is, 94 + patch -R) **before** applying the 5.0.3 patch. You can read more on this in 95 95 :ref:`Documentation/process/applying-patches.rst <applying_patches>`. 96 96 97 97 Alternatively, the script patch-kernel can be used to automate this ··· 114 114 Software requirements 115 115 --------------------- 116 116 117 - Compiling and running the 4.x kernels requires up-to-date 117 + Compiling and running the 5.x kernels requires up-to-date 118 118 versions of various software packages. Consult 119 119 :ref:`Documentation/process/changes.rst <changes>` for the minimum version numbers 120 120 required and how to get updates for these packages. Beware that using ··· 132 132 place for the output files (including .config). 133 133 Example:: 134 134 135 - kernel source code: /usr/src/linux-4.X 135 + kernel source code: /usr/src/linux-5.x 136 136 build directory: /home/name/build/kernel 137 137 138 138 To configure and build the kernel, use:: 139 139 140 - cd /usr/src/linux-4.X 140 + cd /usr/src/linux-5.x 141 141 make O=/home/name/build/kernel menuconfig 142 142 make O=/home/name/build/kernel 143 143 sudo make O=/home/name/build/kernel modules_install install
+61 -56
Documentation/process/applying-patches.rst
··· 216 216 generate a patch representing the differences between two patches and then 217 217 apply the result. 218 218 219 - This will let you move from something like 4.7.2 to 4.7.3 in a single 219 + This will let you move from something like 5.7.2 to 5.7.3 in a single 220 220 step. The -z flag to interdiff will even let you feed it patches in gzip or 221 221 bzip2 compressed form directly without the use of zcat or bzcat or manual 222 222 decompression. 223 223 224 - Here's how you'd go from 4.7.2 to 4.7.3 in a single step:: 224 + Here's how you'd go from 5.7.2 to 5.7.3 in a single step:: 225 225 226 - interdiff -z ../patch-4.7.2.gz ../patch-4.7.3.gz | patch -p1 226 + interdiff -z ../patch-5.7.2.gz ../patch-5.7.3.gz | patch -p1 227 227 228 228 Although interdiff may save you a step or two you are generally advised to 229 229 do the additional steps since interdiff can get things wrong in some cases. ··· 245 245 Most recent patches are linked from the front page, but they also have 246 246 specific homes. 247 247 248 - The 4.x.y (-stable) and 4.x patches live at 248 + The 5.x.y (-stable) and 5.x patches live at 249 249 250 - https://www.kernel.org/pub/linux/kernel/v4.x/ 250 + https://www.kernel.org/pub/linux/kernel/v5.x/ 251 251 252 - The -rc patches live at 252 + The -rc patches are not stored on the webserver but are generated on 253 + demand from git tags such as 253 254 254 - https://www.kernel.org/pub/linux/kernel/v4.x/testing/ 255 + https://git.kernel.org/torvalds/p/v5.1-rc1/v5.0 256 + 257 + The stable -rc patches live at 258 + 259 + https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/ 255 260 256 261 257 - The 4.x kernels 262 + The 5.x kernels 258 263 =============== 259 264 260 265 These are the base stable releases released by Linus. The highest numbered 261 266 release is the most recent. 262 267 263 268 If regressions or other serious flaws are found, then a -stable fix patch 264 - will be released (see below) on top of this base. Once a new 4.x base 269 + will be released (see below) on top of this base. Once a new 5.x base 265 270 kernel is released, a patch is made available that is a delta between the 266 - previous 4.x kernel and the new one. 271 + previous 5.x kernel and the new one. 267 272 268 - To apply a patch moving from 4.6 to 4.7, you'd do the following (note 269 - that such patches do **NOT** apply on top of 4.x.y kernels but on top of the 270 - base 4.x kernel -- if you need to move from 4.x.y to 4.x+1 you need to 271 - first revert the 4.x.y patch). 273 + To apply a patch moving from 5.6 to 5.7, you'd do the following (note 274 + that such patches do **NOT** apply on top of 5.x.y kernels but on top of the 275 + base 5.x kernel -- if you need to move from 5.x.y to 5.x+1 you need to 276 + first revert the 5.x.y patch). 272 277 273 278 Here are some examples:: 274 279 275 - # moving from 4.6 to 4.7 280 + # moving from 5.6 to 5.7 276 281 277 - $ cd ~/linux-4.6 # change to kernel source dir 278 - $ patch -p1 < ../patch-4.7 # apply the 4.7 patch 282 + $ cd ~/linux-5.6 # change to kernel source dir 283 + $ patch -p1 < ../patch-5.7 # apply the 5.7 patch 279 284 $ cd .. 280 - $ mv linux-4.6 linux-4.7 # rename source dir 285 + $ mv linux-5.6 linux-5.7 # rename source dir 281 286 282 - # moving from 4.6.1 to 4.7 287 + # moving from 5.6.1 to 5.7 283 288 284 - $ cd ~/linux-4.6.1 # change to kernel source dir 285 - $ patch -p1 -R < ../patch-4.6.1 # revert the 4.6.1 patch 286 - # source dir is now 4.6 287 - $ patch -p1 < ../patch-4.7 # apply new 4.7 patch 289 + $ cd ~/linux-5.6.1 # change to kernel source dir 290 + $ patch -p1 -R < ../patch-5.6.1 # revert the 5.6.1 patch 291 + # source dir is now 5.6 292 + $ patch -p1 < ../patch-5.7 # apply new 5.7 patch 288 293 $ cd .. 289 - $ mv linux-4.6.1 linux-4.7 # rename source dir 294 + $ mv linux-5.6.1 linux-5.7 # rename source dir 290 295 291 296 292 - The 4.x.y kernels 297 + The 5.x.y kernels 293 298 ================= 294 299 295 300 Kernels with 3-digit versions are -stable kernels. They contain small(ish) 296 301 critical fixes for security problems or significant regressions discovered 297 - in a given 4.x kernel. 302 + in a given 5.x kernel. 298 303 299 304 This is the recommended branch for users who want the most recent stable 300 305 kernel and are not interested in helping test development/experimental 301 306 versions. 302 307 303 - If no 4.x.y kernel is available, then the highest numbered 4.x kernel is 308 + If no 5.x.y kernel is available, then the highest numbered 5.x kernel is 304 309 the current stable kernel. 305 310 306 311 .. note:: ··· 313 308 The -stable team usually do make incremental patches available as well 314 309 as patches against the latest mainline release, but I only cover the 315 310 non-incremental ones below. The incremental ones can be found at 316 - https://www.kernel.org/pub/linux/kernel/v4.x/incr/ 311 + https://www.kernel.org/pub/linux/kernel/v5.x/incr/ 317 312 318 - These patches are not incremental, meaning that for example the 4.7.3 319 - patch does not apply on top of the 4.7.2 kernel source, but rather on top 320 - of the base 4.7 kernel source. 313 + These patches are not incremental, meaning that for example the 5.7.3 314 + patch does not apply on top of the 5.7.2 kernel source, but rather on top 315 + of the base 5.7 kernel source. 321 316 322 - So, in order to apply the 4.7.3 patch to your existing 4.7.2 kernel 323 - source you have to first back out the 4.7.2 patch (so you are left with a 324 - base 4.7 kernel source) and then apply the new 4.7.3 patch. 317 + So, in order to apply the 5.7.3 patch to your existing 5.7.2 kernel 318 + source you have to first back out the 5.7.2 patch (so you are left with a 319 + base 5.7 kernel source) and then apply the new 5.7.3 patch. 325 320 326 321 Here's a small example:: 327 322 328 - $ cd ~/linux-4.7.2 # change to the kernel source dir 329 - $ patch -p1 -R < ../patch-4.7.2 # revert the 4.7.2 patch 330 - $ patch -p1 < ../patch-4.7.3 # apply the new 4.7.3 patch 323 + $ cd ~/linux-5.7.2 # change to the kernel source dir 324 + $ patch -p1 -R < ../patch-5.7.2 # revert the 5.7.2 patch 325 + $ patch -p1 < ../patch-5.7.3 # apply the new 5.7.3 patch 331 326 $ cd .. 332 - $ mv linux-4.7.2 linux-4.7.3 # rename the kernel source dir 327 + $ mv linux-5.7.2 linux-5.7.3 # rename the kernel source dir 333 328 334 329 The -rc kernels 335 330 =============== ··· 348 343 development kernels but do not want to run some of the really experimental 349 344 stuff (such people should see the sections about -next and -mm kernels below). 350 345 351 - The -rc patches are not incremental, they apply to a base 4.x kernel, just 352 - like the 4.x.y patches described above. The kernel version before the -rcN 346 + The -rc patches are not incremental, they apply to a base 5.x kernel, just 347 + like the 5.x.y patches described above. The kernel version before the -rcN 353 348 suffix denotes the version of the kernel that this -rc kernel will eventually 354 349 turn into. 355 350 356 - So, 4.8-rc5 means that this is the fifth release candidate for the 4.8 357 - kernel and the patch should be applied on top of the 4.7 kernel source. 351 + So, 5.8-rc5 means that this is the fifth release candidate for the 5.8 352 + kernel and the patch should be applied on top of the 5.7 kernel source. 358 353 359 354 Here are 3 examples of how to apply these patches:: 360 355 361 - # first an example of moving from 4.7 to 4.8-rc3 356 + # first an example of moving from 5.7 to 5.8-rc3 362 357 363 - $ cd ~/linux-4.7 # change to the 4.7 source dir 364 - $ patch -p1 < ../patch-4.8-rc3 # apply the 4.8-rc3 patch 358 + $ cd ~/linux-5.7 # change to the 5.7 source dir 359 + $ patch -p1 < ../patch-5.8-rc3 # apply the 5.8-rc3 patch 365 360 $ cd .. 366 - $ mv linux-4.7 linux-4.8-rc3 # rename the source dir 361 + $ mv linux-5.7 linux-5.8-rc3 # rename the source dir 367 362 368 - # now let's move from 4.8-rc3 to 4.8-rc5 363 + # now let's move from 5.8-rc3 to 5.8-rc5 369 364 370 - $ cd ~/linux-4.8-rc3 # change to the 4.8-rc3 dir 371 - $ patch -p1 -R < ../patch-4.8-rc3 # revert the 4.8-rc3 patch 372 - $ patch -p1 < ../patch-4.8-rc5 # apply the new 4.8-rc5 patch 365 + $ cd ~/linux-5.8-rc3 # change to the 5.8-rc3 dir 366 + $ patch -p1 -R < ../patch-5.8-rc3 # revert the 5.8-rc3 patch 367 + $ patch -p1 < ../patch-5.8-rc5 # apply the new 5.8-rc5 patch 373 368 $ cd .. 374 - $ mv linux-4.8-rc3 linux-4.8-rc5 # rename the source dir 369 + $ mv linux-5.8-rc3 linux-5.8-rc5 # rename the source dir 375 370 376 - # finally let's try and move from 4.7.3 to 4.8-rc5 371 + # finally let's try and move from 5.7.3 to 5.8-rc5 377 372 378 - $ cd ~/linux-4.7.3 # change to the kernel source dir 379 - $ patch -p1 -R < ../patch-4.7.3 # revert the 4.7.3 patch 380 - $ patch -p1 < ../patch-4.8-rc5 # apply new 4.8-rc5 patch 373 + $ cd ~/linux-5.7.3 # change to the kernel source dir 374 + $ patch -p1 -R < ../patch-5.7.3 # revert the 5.7.3 patch 375 + $ patch -p1 < ../patch-5.8-rc5 # apply new 5.8-rc5 patch 381 376 $ cd .. 382 - $ mv linux-4.7.3 linux-4.8-rc5 # rename the kernel source dir 377 + $ mv linux-5.7.3 linux-5.8-rc5 # rename the kernel source dir 383 378 384 379 385 380 The -mm patches and the linux-next tree
+1 -1
Documentation/translations/it_IT/admin-guide/README.rst
··· 4 4 5 5 .. _it_readme: 6 6 7 - Rilascio del kernel Linux 4.x <http://kernel.org/> 7 + Rilascio del kernel Linux 5.x <http://kernel.org/> 8 8 =================================================== 9 9 10 10 .. warning::