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

Merge tag 'docs-5.8-2' of git://git.lwn.net/linux

Pull more documentation updates from Jonathan Corbet:
"A handful of late-arriving docs fixes, along with a patch changing a
lot of HTTP links to HTTPS that had to be yanked and redone before the
first pull"

* tag 'docs-5.8-2' of git://git.lwn.net/linux:
docs/memory-barriers.txt/kokr: smp_mb__{before,after}_atomic(): update Documentation
Documentation: devres: add missing entry for devm_platform_get_and_ioremap_resource()
Replace HTTP links with HTTPS ones: documentation
docs: it_IT: address invalid reference warnings
doc: zh_CN: use doc reference to resolve undefined label warning
docs: Update the location of the LF NDA program
docs: dev-tools: coccinelle: underlines

+90 -82
+8 -8
Documentation/admin-guide/LSM/tomoyo.rst
··· 27 27 ======================= 28 28 29 29 User <-> Kernel interface documentation is available at 30 - http://tomoyo.osdn.jp/2.5/policy-specification/index.html . 30 + https://tomoyo.osdn.jp/2.5/policy-specification/index.html . 31 31 32 32 Materials we prepared for seminars and symposiums are available at 33 - http://osdn.jp/projects/tomoyo/docs/?category_id=532&language_id=1 . 33 + https://osdn.jp/projects/tomoyo/docs/?category_id=532&language_id=1 . 34 34 Below lists are chosen from three aspects. 35 35 36 36 What is TOMOYO? 37 37 TOMOYO Linux Overview 38 - http://osdn.jp/projects/tomoyo/docs/lca2009-takeda.pdf 38 + https://osdn.jp/projects/tomoyo/docs/lca2009-takeda.pdf 39 39 TOMOYO Linux: pragmatic and manageable security for Linux 40 - http://osdn.jp/projects/tomoyo/docs/freedomhectaipei-tomoyo.pdf 40 + https://osdn.jp/projects/tomoyo/docs/freedomhectaipei-tomoyo.pdf 41 41 TOMOYO Linux: A Practical Method to Understand and Protect Your Own Linux Box 42 - http://osdn.jp/projects/tomoyo/docs/PacSec2007-en-no-demo.pdf 42 + https://osdn.jp/projects/tomoyo/docs/PacSec2007-en-no-demo.pdf 43 43 44 44 What can TOMOYO do? 45 45 Deep inside TOMOYO Linux 46 - http://osdn.jp/projects/tomoyo/docs/lca2009-kumaneko.pdf 46 + https://osdn.jp/projects/tomoyo/docs/lca2009-kumaneko.pdf 47 47 The role of "pathname based access control" in security. 48 - http://osdn.jp/projects/tomoyo/docs/lfj2008-bof.pdf 48 + https://osdn.jp/projects/tomoyo/docs/lfj2008-bof.pdf 49 49 50 50 History of TOMOYO? 51 51 Realities of Mainlining 52 - http://osdn.jp/projects/tomoyo/docs/lfj2008.pdf 52 + https://osdn.jp/projects/tomoyo/docs/lfj2008.pdf 53 53 54 54 What is future plan? 55 55 ====================
+1 -1
Documentation/admin-guide/acpi/initrd_table_override.rst
··· 102 102 ================================= 103 103 104 104 iasl and acpixtract are part of Intel's ACPICA project: 105 - http://acpica.org/ 105 + https://acpica.org/ 106 106 107 107 and should be packaged by distributions (for example in the acpica package 108 108 on SUSE).
+2 -2
Documentation/admin-guide/bcache.rst
··· 7 7 8 8 Wiki and git repositories are at: 9 9 10 - - http://bcache.evilpiepirate.org 10 + - https://bcache.evilpiepirate.org 11 11 - http://evilpiepirate.org/git/linux-bcache.git 12 - - http://evilpiepirate.org/git/bcache-tools.git 12 + - https://evilpiepirate.org/git/bcache-tools.git 13 13 14 14 It's designed around the performance characteristics of SSDs - it only allocates 15 15 in erase block sized buckets, and it uses a hybrid btree/log to track cached
+1 -1
Documentation/admin-guide/devices.rst
··· 17 17 to involve for character and block devices. 18 18 19 19 This document is included by reference into the Filesystem Hierarchy 20 - Standard (FHS). The FHS is available from http://www.pathname.com/fhs/. 20 + Standard (FHS). The FHS is available from https://www.pathname.com/fhs/. 21 21 22 22 Allocations marked (68k/Amiga) apply to Linux/68k on the Amiga 23 23 platform only. Allocations marked (68k/Atari) apply to Linux/68k on
+1 -1
Documentation/admin-guide/initrd.rst
··· 376 376 --------- 377 377 378 378 .. [#f1] Almesberger, Werner; "Booting Linux: The History and the Future" 379 - http://www.almesberger.net/cv/papers/ols2k-9.ps.gz 379 + https://www.almesberger.net/cv/papers/ols2k-9.ps.gz 380 380 .. [#f2] newlib package (experimental), with initrd example 381 381 https://www.sourceware.org/newlib/ 382 382 .. [#f3] util-linux: Miscellaneous utilities for Linux
+1 -1
Documentation/admin-guide/md.rst
··· 5 5 --------------------------------- 6 6 7 7 Tools that manage md devices can be found at 8 - http://www.kernel.org/pub/linux/utils/raid/ 8 + https://www.kernel.org/pub/linux/utils/raid/ 9 9 10 10 11 11 You can boot with your md device with the following kernel command
+2 -2
Documentation/admin-guide/mono.rst
··· 12 12 a binary package, a source tarball or by installing from Git. Binary 13 13 packages for several distributions can be found at: 14 14 15 - http://www.mono-project.com/download/ 15 + https://www.mono-project.com/download/ 16 16 17 17 Instructions for compiling Mono can be found at: 18 18 19 - http://www.mono-project.com/docs/compiling-mono/linux/ 19 + https://www.mono-project.com/docs/compiling-mono/linux/ 20 20 21 21 Once the Mono CLR support has been installed, just check that 22 22 ``/usr/bin/mono`` (which could be located elsewhere, for example
+1 -1
Documentation/admin-guide/reporting-bugs.rst
··· 75 75 76 76 If you haven't reported a bug before, please read: 77 77 78 - http://www.chiark.greenend.org.uk/~sgtatham/bugs.html 78 + https://www.chiark.greenend.org.uk/~sgtatham/bugs.html 79 79 80 80 http://www.catb.org/esr/faqs/smart-questions.html 81 81
+2 -2
Documentation/admin-guide/unicode.rst
··· 114 114 This range is now officially managed by the ConScript Unicode 115 115 Registry. The normative reference is at: 116 116 117 - http://www.evertype.com/standards/csur/klingon.html 117 + https://www.evertype.com/standards/csur/klingon.html 118 118 119 119 Klingon has an alphabet of 26 characters, a positional numeric writing 120 120 system with 10 digits, and is written left-to-right, top-to-bottom. ··· 178 178 <jcowan@reutershealth.com> and Michael Everson <everson@evertype.com>. 179 179 The ConScript Unicode Registry is accessible at: 180 180 181 - http://www.evertype.com/standards/csur/ 181 + https://www.evertype.com/standards/csur/ 182 182 183 183 The ranges used fall at the low end of the End User Zone and can hence 184 184 not be normatively assigned, but it is recommended that people who
+1 -1
Documentation/conf.py
··· 538 538 # Grouping the document tree into PDF files. List of tuples 539 539 # (source start file, target name, title, author, options). 540 540 # 541 - # See the Sphinx chapter of http://ralsina.me/static/manual.pdf 541 + # See the Sphinx chapter of https://ralsina.me/static/manual.pdf 542 542 # 543 543 # FIXME: Do not add the index file here; the result will be too big. Adding 544 544 # multiple PDF files here actually tries to get the cross-referencing right
+2 -2
Documentation/core-api/rbtree.rst
··· 36 36 information on the nature and implementation of Red Black Trees, see: 37 37 38 38 Linux Weekly News article on red-black trees 39 - http://lwn.net/Articles/184495/ 39 + https://lwn.net/Articles/184495/ 40 40 41 41 Wikipedia entry on red-black trees 42 - http://en.wikipedia.org/wiki/Red-black_tree 42 + https://en.wikipedia.org/wiki/Red-black_tree 43 43 44 44 Linux implementation of red-black trees 45 45 ---------------------------------------
+4 -4
Documentation/dev-tools/coccinelle.rst
··· 14 14 tree-wide patches and detection of problematic programming patterns. 15 15 16 16 Getting Coccinelle 17 - ------------------- 17 + ------------------ 18 18 19 19 The semantic patches included in the kernel use features and options 20 20 which are provided by Coccinelle version 1.0.0-rc11 and above. ··· 56 56 https://github.com/coccinelle/coccinelle/blob/master/install.txt 57 57 58 58 Supplemental documentation 59 - --------------------------- 59 + -------------------------- 60 60 61 61 For supplemental documentation refer to the wiki: 62 62 ··· 128 128 make coccicheck MODE=report V=1 129 129 130 130 Coccinelle parallelization 131 - --------------------------- 131 + -------------------------- 132 132 133 133 By default, coccicheck tries to run as parallel as possible. To change 134 134 the parallelism, set the J= variable. For example, to run across 4 CPUs:: ··· 333 333 // Requires: 1.0.5 334 334 335 335 Proposing new semantic patches 336 - ------------------------------- 336 + ------------------------------ 337 337 338 338 New semantic patches can be proposed and submitted by kernel 339 339 developers. For sake of clarity, they should be organized in the
+1 -1
Documentation/dev-tools/gdb-kernel-debugging.rst
··· 24 24 25 25 - Create a virtual Linux machine for QEMU/KVM (see www.linux-kvm.org and 26 26 www.qemu.org for more details). For cross-development, 27 - http://landley.net/aboriginal/bin keeps a pool of machine images and 27 + https://landley.net/aboriginal/bin keeps a pool of machine images and 28 28 toolchains that can be helpful to start from. 29 29 30 30 - Build the kernel with CONFIG_GDB_SCRIPTS enabled, but leave
+1 -1
Documentation/doc-guide/parse-headers.rst
··· 186 186 187 187 Copyright (c) 2016 by Mauro Carvalho Chehab <mchehab+samsung@kernel.org>. 188 188 189 - License GPLv2: GNU GPL version 2 <http://gnu.org/licenses/gpl.html>. 189 + License GPLv2: GNU GPL version 2 <https://gnu.org/licenses/gpl.html>. 190 190 191 191 This is free software: you are free to change and redistribute it. 192 192 There is NO WARRANTY, to the extent permitted by law.
+3 -3
Documentation/driver-api/acpi/linuxized-acpica.rst
··· 175 175 B. acpica / master - "master" branch of the git repository at 176 176 <https://github.com/acpica/acpica.git>. 177 177 C. linux-pm / linux-next - "linux-next" branch of the git repository at 178 - <http://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git>. 178 + <https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git>. 179 179 D. linux / master - "master" branch of the git repository at 180 - <http://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git>. 180 + <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git>. 181 181 182 182 Before the linuxized ACPICA patches are sent to the Linux ACPI community 183 183 for review, there is a quality assurance build test process to reduce ··· 274 274 a diff file indicating the state of the current divergences:: 275 275 276 276 # git clone https://github.com/acpica/acpica 277 - # git clone http://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 277 + # git clone https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 278 278 # cd acpica 279 279 # generate/linux/divergences.sh -s ../linux
+1
Documentation/driver-api/driver-model/devres.rst
··· 314 314 devm_platform_ioremap_resource() : calls devm_ioremap_resource() for platform device 315 315 devm_platform_ioremap_resource_wc() 316 316 devm_platform_ioremap_resource_byname() 317 + devm_platform_get_and_ioremap_resource() 317 318 devm_iounmap() 318 319 pcim_iomap() 319 320 pcim_iomap_regions() : do request_region() and iomap() on multiple BARs
+2 -2
Documentation/driver-api/usb/bulk-streams.rst
··· 9 9 queued at once. 10 10 11 11 Streams are defined in sections 4.4.6.4 and 8.12.1.4 of the Universal Serial Bus 12 - 3.0 specification at http://www.usb.org/developers/docs/ The USB Attached SCSI 12 + 3.0 specification at https://www.usb.org/developers/docs/ The USB Attached SCSI 13 13 Protocol, which uses streams to queue multiple SCSI commands, can be found on 14 - the T10 website (http://t10.org/). 14 + the T10 website (https://t10.org/). 15 15 16 16 17 17 Device-side implications
+3 -3
Documentation/driver-api/usb/writing_musb_glue_layer.rst
··· 707 707 Resources 708 708 ========= 709 709 710 - USB Home Page: http://www.usb.org 710 + USB Home Page: https://www.usb.org 711 711 712 - linux-usb Mailing List Archives: http://marc.info/?l=linux-usb 712 + linux-usb Mailing List Archives: https://marc.info/?l=linux-usb 713 713 714 714 USB On-the-Go Basics: 715 - http://www.maximintegrated.com/app-notes/index.mvp/id/1822 715 + https://www.maximintegrated.com/app-notes/index.mvp/id/1822 716 716 717 717 :ref:`Writing USB Device Drivers <writing-usb-driver>` 718 718
+1 -1
Documentation/filesystems/path-lookup.txt
··· 375 375 Papers and other documentation on dcache locking 376 376 ================================================ 377 377 378 - 1. Scaling dcache with RCU (http://linuxjournal.com/article.php?sid=7124). 378 + 1. Scaling dcache with RCU (https://linuxjournal.com/article.php?sid=7124). 379 379 380 380 2. http://lse.sourceforge.net/locking/dcache/dcache.html 381 381
+2 -2
Documentation/filesystems/seq_file.rst
··· 7 7 Copyright 2003 Jonathan Corbet <corbet@lwn.net> 8 8 9 9 This file is originally from the LWN.net Driver Porting series at 10 - http://lwn.net/Articles/driver-porting/ 10 + https://lwn.net/Articles/driver-porting/ 11 11 12 12 13 13 There are numerous ways for a device driver (or other kernel component) to ··· 57 57 result. Yes, it is a thoroughly useless module, but the point is to show 58 58 how the mechanism works without getting lost in other details. (Those 59 59 wanting to see the full source for this module can find it at 60 - http://lwn.net/Articles/22359/). 60 + https://lwn.net/Articles/22359/). 61 61 62 62 Deprecated create_proc_entry 63 63 ============================
+3 -3
Documentation/misc-devices/c2port.txt
··· 28 28 References 29 29 ---------- 30 30 31 - The C2 Interface main references are at (http://www.silabs.com) 31 + The C2 Interface main references are at (https://www.silabs.com) 32 32 Silicon Laboratories site], see: 33 33 34 34 - AN127: FLASH Programming via the C2 Interface at 35 - http://www.silabs.com/Support Documents/TechnicalDocs/an127.pdf 35 + https://www.silabs.com/Support Documents/TechnicalDocs/an127.pdf 36 36 37 37 - C2 Specification at 38 - http://www.silabs.com/pages/DownloadDoc.aspx?FILEURL=Support%20Documents/TechnicalDocs/an127.pdf&src=SearchResults 38 + https://www.silabs.com/pages/DownloadDoc.aspx?FILEURL=Support%20Documents/TechnicalDocs/an127.pdf&src=SearchResults 39 39 40 40 however it implements a two wire serial communication protocol (bit 41 41 banging) designed to enable in-system programming, debugging, and
+2 -2
Documentation/process/3.Early-stage.rst
··· 46 46 to communicate user requirements to these people is a waste of 47 47 time. They are much too "intelligent" to listen to lesser mortals. 48 48 49 - (http://lwn.net/Articles/131776/). 49 + (https://lwn.net/Articles/131776/). 50 50 51 51 The reality of the situation was different; the kernel developers were far 52 52 more concerned about system stability, long-term maintenance, and finding ··· 216 216 designed to help with this sort of situation; more information can be found 217 217 at: 218 218 219 - http://www.linuxfoundation.org/en/NDA_program 219 + https://www.linuxfoundation.org/nda/ 220 220 221 221 This kind of review is often enough to avoid serious problems later on 222 222 without requiring public disclosure of the project.
+4 -4
Documentation/process/7.AdvancedTopics.rst
··· 29 29 fits into the kernel development process in particular. Developers who 30 30 wish to come up to speed with git will find more information at: 31 31 32 - http://git-scm.com/ 32 + https://git-scm.com/ 33 33 34 - http://www.kernel.org/pub/software/scm/git/docs/user-manual.html 34 + https://www.kernel.org/pub/software/scm/git/docs/user-manual.html 35 35 36 36 and on various tutorials found on the web. 37 37 ··· 55 55 which is accessible to the Internet. Otherwise, free, public hosting sites 56 56 (Github, for example) are starting to appear on the net. Established 57 57 developers can get an account on kernel.org, but those are not easy to come 58 - by; see http://kernel.org/faq/ for more information. 58 + by; see https://kernel.org/faq/ for more information. 59 59 60 60 The normal git workflow involves the use of a lot of branches. Each line 61 61 of development can be separated into a separate "topic branch" and ··· 125 125 to trust things *without* then having to go and check every 126 126 individual change by hand. 127 127 128 - (http://lwn.net/Articles/224135/). 128 + (https://lwn.net/Articles/224135/). 129 129 130 130 To avoid this kind of situation, ensure that all patches within a given 131 131 branch stick closely to the associated topic; a "driver fixes" branch
+7 -7
Documentation/process/8.Conclusion.rst
··· 16 16 properly). 17 17 18 18 Various web sites discuss kernel development at all levels of detail. Your 19 - author would like to humbly suggest http://lwn.net/ as a source; 19 + author would like to humbly suggest https://lwn.net/ as a source; 20 20 information on many specific kernel topics can be found via the LWN kernel 21 21 index at: 22 22 23 - http://lwn.net/Kernel/Index/ 23 + https://lwn.net/Kernel/Index/ 24 24 25 25 Beyond that, a valuable resource for kernel developers is: 26 26 27 - http://kernelnewbies.org/ 27 + https://kernelnewbies.org/ 28 28 29 - And, of course, one should not forget http://kernel.org/, the definitive 29 + And, of course, one should not forget https://kernel.org/, the definitive 30 30 location for kernel release information. 31 31 32 32 There are a number of books on kernel development: 33 33 34 34 Linux Device Drivers, 3rd Edition (Jonathan Corbet, Alessandro 35 35 Rubini, and Greg Kroah-Hartman). Online at 36 - http://lwn.net/Kernel/LDD3/. 36 + https://lwn.net/Kernel/LDD3/. 37 37 38 38 Linux Kernel Development (Robert Love). 39 39 ··· 46 46 47 47 Documentation for git can be found at: 48 48 49 - http://www.kernel.org/pub/software/scm/git/docs/ 49 + https://www.kernel.org/pub/software/scm/git/docs/ 50 50 51 - http://www.kernel.org/pub/software/scm/git/docs/user-manual.html 51 + https://www.kernel.org/pub/software/scm/git/docs/user-manual.html 52 52 53 53 54 54 Conclusion
+2 -2
Documentation/process/adding-syscalls.rst
··· 541 541 :manpage:`syscall(2)` man-page: 542 542 http://man7.org/linux/man-pages/man2/syscall.2.html#NOTES 543 543 - Collated emails from Linus Torvalds discussing the problems with ``ioctl()``: 544 - http://yarchive.net/comp/linux/ioctl.html 544 + https://yarchive.net/comp/linux/ioctl.html 545 545 - "How to not invent kernel interfaces", Arnd Bergmann, 546 - http://www.ukuug.org/events/linux2007/2007/papers/Bergmann.pdf 546 + https://www.ukuug.org/events/linux2007/2007/papers/Bergmann.pdf 547 547 - LWN article from Michael Kerrisk on avoiding new uses of CAP_SYS_ADMIN: 548 548 https://lwn.net/Articles/486306/ 549 549 - Recommendation from Andrew Morton that all related information for a new
+2 -2
Documentation/process/applying-patches.rst
··· 229 229 do the additional steps since interdiff can get things wrong in some cases. 230 230 231 231 Another alternative is ``ketchup``, which is a python script for automatic 232 - downloading and applying of patches (http://www.selenic.com/ketchup/). 232 + downloading and applying of patches (https://www.selenic.com/ketchup/). 233 233 234 234 Other nice tools are diffstat, which shows a summary of changes made by a 235 235 patch; lsdiff, which displays a short listing of affected files in a patch ··· 241 241 Where can I download the patches? 242 242 ================================= 243 243 244 - The patches are available at http://kernel.org/ 244 + The patches are available at https://kernel.org/ 245 245 Most recent patches are linked from the front page, but they also have 246 246 specific homes. 247 247
+2 -2
Documentation/process/volatile-considered-harmful.rst
··· 109 109 References 110 110 ========== 111 111 112 - [1] http://lwn.net/Articles/233481/ 112 + [1] https://lwn.net/Articles/233481/ 113 113 114 - [2] http://lwn.net/Articles/233482/ 114 + [2] https://lwn.net/Articles/233482/ 115 115 116 116 Credits 117 117 =======
+1 -1
Documentation/security/SCTP.rst
··· 328 328 label (see **netlabel-config**\(8) helper script for details). 329 329 330 330 5) The NetLabel SCTP peer labeling rules apply as discussed in the following 331 - set of posts tagged "netlabel" at: http://www.paul-moore.com/blog/t. 331 + set of posts tagged "netlabel" at: https://www.paul-moore.com/blog/t. 332 332 333 333 6) CIPSO is only supported for IPv4 addressing: ``socket(AF_INET, ...)`` 334 334 CALIPSO is only supported for IPv6 addressing: ``socket(AF_INET6, ...)``
+3 -3
Documentation/sphinx/kfigure.py
··· 29 29 30 30 Used tools: 31 31 32 - * ``dot(1)``: Graphviz (http://www.graphviz.org). If Graphviz is not 32 + * ``dot(1)``: Graphviz (https://www.graphviz.org). If Graphviz is not 33 33 available, the DOT language is inserted as literal-block. 34 34 35 35 * SVG to PDF: To generate PDF, you need at least one of this tools: ··· 41 41 * generate PDF from SVG / used by PDF (LaTeX) builder 42 42 43 43 * generate SVG (html-builder) and PDF (latex-builder) from DOT files. 44 - DOT: see http://www.graphviz.org/content/dot-language 44 + DOT: see https://www.graphviz.org/content/dot-language 45 45 46 46 """ 47 47 ··· 182 182 kernellog.verbose(app, "use dot(1) from: " + dot_cmd) 183 183 else: 184 184 kernellog.warn(app, "dot(1) not found, for better output quality install " 185 - "graphviz from http://www.graphviz.org") 185 + "graphviz from https://www.graphviz.org") 186 186 if convert_cmd: 187 187 kernellog.verbose(app, "use convert(1) from: " + convert_cmd) 188 188 else:
+1 -1
Documentation/static-keys.txt
··· 71 71 72 72 gcc (v4.5) adds a new 'asm goto' statement that allows branching to a label: 73 73 74 - http://gcc.gnu.org/ml/gcc-patches/2009-07/msg01556.html 74 + https://gcc.gnu.org/ml/gcc-patches/2009-07/msg01556.html 75 75 76 76 Using the 'asm goto', we can create branches that are either taken or not taken 77 77 by default, without the need to check memory. Then, at run-time, we can patch
+1 -1
Documentation/trace/events-msr.rst
··· 4 4 5 5 The x86 kernel supports tracing most MSR (Model Specific Register) accesses. 6 6 To see the definition of the MSRs on Intel systems please see the SDM 7 - at http://www.intel.com/sdm (Volume 3) 7 + at https://www.intel.com/sdm (Volume 3) 8 8 9 9 Available trace points: 10 10
+1 -1
Documentation/trace/mmiotrace.rst
··· 5 5 6 6 Home page and links to optional user space tools: 7 7 8 - http://nouveau.freedesktop.org/wiki/MmioTrace 8 + https://nouveau.freedesktop.org/wiki/MmioTrace 9 9 10 10 MMIO tracing was originally developed by Intel around 2003 for their Fault 11 11 Injection Test Harness. In Dec 2006 - Jan 2007, using the code from Intel,
+2 -2
Documentation/translations/it_IT/kernel-hacking/hacking.rst
··· 634 634 635 635 Questa è una variate di `EXPORT_SYMBOL()` che permette di specificare uno 636 636 spazio dei nomi. Lo spazio dei nomi è documentato in 637 - :doc:`../core-api/symbol-namespaces` 637 + :doc:`../../../core-api/symbol-namespaces` 638 638 639 639 :c:func:`EXPORT_SYMBOL_NS_GPL()` 640 640 -------------------------------- ··· 643 643 644 644 Questa è una variate di `EXPORT_SYMBOL_GPL()` che permette di specificare uno 645 645 spazio dei nomi. Lo spazio dei nomi è documentato in 646 - :doc:`../core-api/symbol-namespaces` 646 + :doc:`../../../core-api/symbol-namespaces` 647 647 648 648 Procedure e convenzioni 649 649 =======================
+2
Documentation/translations/it_IT/process/email-clients.rst
··· 3 3 :Original: :doc:`../../../process/email-clients` 4 4 :Translator: Alessia Mantegazza <amantegazza@vaga.pv.it> 5 5 6 + .. _it_email_clients: 7 + 6 8 Informazioni sui programmi di posta elettronica per Linux 7 9 ========================================================= 8 10
+2
Documentation/translations/it_IT/process/management-style.rst
··· 3 3 :Original: :doc:`../../../process/management-style` 4 4 :Translator: Alessia Mantegazza <amantegazza@vaga.pv.it> 5 5 6 + .. _it_managementstyle: 7 + 6 8 Il modello di gestione del kernel Linux 7 9 ======================================= 8 10
+8 -5
Documentation/translations/ko_KR/memory-barriers.txt
··· 1842 1842 (*) smp_mb__before_atomic(); 1843 1843 (*) smp_mb__after_atomic(); 1844 1844 1845 - 이것들은 값을 리턴하지 않는 (더하기, 빼기, 증가, 감소와 같은) 어토믹 1846 - 함수들을 위한, 특히 그것들이 레퍼런스 카운팅에 사용될 때를 위한 1847 - 함수들입니다. 이 함수들은 메모리 배리어를 내포하고 있지는 않습니다. 1845 + 이것들은 메모리 배리어를 내포하지 않는 어토믹 RMW 함수를 사용하지만 코드에 1846 + 메모리 배리어가 필요한 경우를 위한 것들입니다. 메모리 배리어를 내포하지 1847 + 않는 어토믹 RMW 함수들의 예로는 더하기, 빼기, (실패한) 조건적 1848 + 오퍼레이션들, _relaxed 함수들이 있으며, atomic_read 나 atomic_set 은 이에 1849 + 해당되지 않습니다. 메모리 배리어가 필요해지는 흔한 예로는 어토믹 1850 + 오퍼레이션을 사용해 레퍼런스 카운트를 수정하는 경우를 들 수 있습니다. 1848 1851 1849 - 이것들은 값을 리턴하지 않으며 어토믹한 (set_bit 과 clear_bit 같은) 비트 1850 - 연산에도 사용될 수 있습니다. 1852 + 이것들은 또한 (set_bit 과 clear_bit 같은) 메모리 배리어를 내포하지 않는 1853 + 어토믹 RMW bitop 함수들을 위해서도 사용될 수 있습니다. 1851 1854 1852 1855 한 예로, 객체 하나를 무효한 것으로 표시하고 그 객체의 레퍼런스 카운트를 1853 1856 감소시키는 다음 코드를 보세요:
+1 -1
Documentation/translations/zh_CN/filesystems/debugfs.rst
··· 2 2 3 3 .. include:: ../disclaimer-zh_CN.rst 4 4 5 - :Original: :ref:`Documentation/filesystems/debugfs.txt <debugfs_index>` 5 + :Original: :doc:`../../../filesystems/debugfs` 6 6 7 7 ======= 8 8 Debugfs
+1 -1
Documentation/vm/ksm.rst
··· 6 6 7 7 KSM is a memory-saving de-duplication feature, enabled by CONFIG_KSM=y, 8 8 added to the Linux kernel in 2.6.32. See ``mm/ksm.c`` for its implementation, 9 - and http://lwn.net/Articles/306704/ and http://lwn.net/Articles/330589/ 9 + and http://lwn.net/Articles/306704/ and https://lwn.net/Articles/330589/ 10 10 11 11 The userspace interface of KSM is described in :ref:`Documentation/admin-guide/mm/ksm.rst <admin_guide_ksm>` 12 12
+3 -3
Documentation/xz.txt
··· 14 14 The XZ decompressor in Linux is called XZ Embedded. It supports 15 15 the LZMA2 filter and optionally also BCJ filters. CRC32 is supported 16 16 for integrity checking. The home page of XZ Embedded is at 17 - <http://tukaani.org/xz/embedded.html>, where you can find the 17 + <https://tukaani.org/xz/embedded.html>, where you can find the 18 18 latest version and also information about using the code outside 19 19 the Linux kernel. 20 20 21 21 For userspace, XZ Utils provide a zlib-like compression library 22 22 and a gzip-like command line tool. XZ Utils can be downloaded from 23 - <http://tukaani.org/xz/>. 23 + <https://tukaani.org/xz/>. 24 24 25 25 XZ related components in the kernel 26 26 =================================== ··· 113 113 ============== 114 114 115 115 Before reporting a bug, please check that it's not fixed already 116 - at upstream. See <http://tukaani.org/xz/embedded.html> to get the 116 + at upstream. See <https://tukaani.org/xz/embedded.html> to get the 117 117 latest code. 118 118 119 119 Report bugs to <lasse.collin@tukaani.org> or visit #tukaani on
+1 -1
scripts/kernel-doc
··· 321 321 322 322 # Generated docbook code is inserted in a template at a point where 323 323 # docbook v3.1 requires a non-zero sequence of RefEntry's; see: 324 - # http://www.oasis-open.org/docbook/documentation/reference/html/refentry.html 324 + # https://www.oasis-open.org/docbook/documentation/reference/html/refentry.html 325 325 # We keep track of number of generated entries and generate a dummy 326 326 # if needs be to ensure the expanded template can be postprocessed 327 327 # into html.