forked from Minki/linux
Replace HTTP links with HTTPS ones: Documentation/driver-api
Rationale: Reduces attack surface on kernel devs opening the links for MITM as HTTPS traffic is much harder to manipulate. Deterministic algorithm: For each file: If not .svg: For each line: If doesn't contain `\bxmlns\b`: For each link, `\bhttp://[^# \t\r\n]*(?:\w|/)`: If both the HTTP and HTTPS versions return 200 OK and serve the same content: Replace HTTP with HTTPS. Signed-off-by: Alexander A. Klimov <grandmaster@al2klimov.de> Link: https://lore.kernel.org/r/20200621133512.46311-1-grandmaster@al2klimov.de Signed-off-by: Jonathan Corbet <corbet@lwn.net>
This commit is contained in:
parent
c5f95886fa
commit
d3603f4c30
@ -92,7 +92,7 @@ You can obtain somewhat infrequent snapshots of klibc from
|
||||
https://www.kernel.org/pub/linux/libs/klibc/
|
||||
|
||||
For active users, you are better off using the klibc git
|
||||
repository, at http://git.kernel.org/?p=libs/klibc/klibc.git
|
||||
repository, at https://git.kernel.org/?p=libs/klibc/klibc.git
|
||||
|
||||
The standalone klibc distribution currently provides three components,
|
||||
in addition to the klibc library:
|
||||
@ -122,7 +122,7 @@ and a number of other utilities, so you can replace kinit and build
|
||||
custom initramfs images that meet your needs exactly.
|
||||
|
||||
For questions and help, you can sign up for the early userspace
|
||||
mailing list at http://www.zytor.com/mailman/listinfo/klibc
|
||||
mailing list at https://www.zytor.com/mailman/listinfo/klibc
|
||||
|
||||
How does it work?
|
||||
=================
|
||||
|
@ -14,7 +14,7 @@ memory devices like
|
||||
* Pseudo-SRAM devices
|
||||
|
||||
GPMC is found on Texas Instruments SoC's (OMAP based)
|
||||
IP details: http://www.ti.com/lit/pdf/spruh73 section 7.1
|
||||
IP details: https://www.ti.com/lit/pdf/spruh73 section 7.1
|
||||
|
||||
|
||||
GPMC generic timing calculation:
|
||||
|
@ -5,7 +5,7 @@ MMC tools introduction
|
||||
There is one MMC test tools called mmc-utils, which is maintained by Chris Ball,
|
||||
you can find it at the below public git repository:
|
||||
|
||||
http://git.kernel.org/cgit/linux/kernel/git/cjb/mmc-utils.git/
|
||||
https://git.kernel.org/cgit/linux/kernel/git/cjb/mmc-utils.git/
|
||||
|
||||
Functions
|
||||
=========
|
||||
|
@ -113,13 +113,13 @@ Supporting Documents
|
||||
--------------------
|
||||
|
||||
ACPI 6:
|
||||
http://www.uefi.org/sites/default/files/resources/ACPI_6.0.pdf
|
||||
https://www.uefi.org/sites/default/files/resources/ACPI_6.0.pdf
|
||||
NVDIMM Namespace:
|
||||
http://pmem.io/documents/NVDIMM_Namespace_Spec.pdf
|
||||
https://pmem.io/documents/NVDIMM_Namespace_Spec.pdf
|
||||
DSM Interface Example:
|
||||
http://pmem.io/documents/NVDIMM_DSM_Interface_Example.pdf
|
||||
https://pmem.io/documents/NVDIMM_DSM_Interface_Example.pdf
|
||||
Driver Writer's Guide:
|
||||
http://pmem.io/documents/NVDIMM_Driver_Writers_Guide.pdf
|
||||
https://pmem.io/documents/NVDIMM_Driver_Writers_Guide.pdf
|
||||
|
||||
Git Trees
|
||||
---------
|
||||
@ -778,7 +778,7 @@ Why the Term "namespace"?
|
||||
|
||||
2. The term originated to describe the sub-devices that can be created
|
||||
within a NVME controller (see the nvme specification:
|
||||
http://www.nvmexpress.org/specifications/), and NFIT namespaces are
|
||||
https://www.nvmexpress.org/specifications/), and NFIT namespaces are
|
||||
meant to parallel the capabilities and configurability of
|
||||
NVME-namespaces.
|
||||
|
||||
@ -786,7 +786,7 @@ Why the Term "namespace"?
|
||||
LIBNVDIMM/LIBNDCTL: Block Translation Table "btt"
|
||||
-------------------------------------------------
|
||||
|
||||
A BTT (design document: http://pmem.io/2014/09/23/btt.html) is a stacked
|
||||
A BTT (design document: https://pmem.io/2014/09/23/btt.html) is a stacked
|
||||
block device driver that fronts either the whole block device or a
|
||||
partition of a block device emitted by either a PMEM or BLK NAMESPACE.
|
||||
|
||||
|
@ -138,6 +138,6 @@ another encrypted-key.
|
||||
This command is only available when the master security is enabled, indicated
|
||||
by the extended security status.
|
||||
|
||||
[1]: http://pmem.io/documents/NVDIMM_DSM_Interface-V1.8.pdf
|
||||
[1]: https://pmem.io/documents/NVDIMM_DSM_Interface-V1.8.pdf
|
||||
|
||||
[2]: http://www.t13.org/documents/UploadedDocuments/docs2006/e05179r4-ACS-SecurityClarifications.pdf
|
||||
|
@ -356,7 +356,7 @@ NOTE:
|
||||
http://www.rapidio.org/education/technology_comparisons/
|
||||
|
||||
[3] RapidIO support for Linux.
|
||||
http://lwn.net/Articles/139118/
|
||||
https://lwn.net/Articles/139118/
|
||||
|
||||
[4] Matt Porter. RapidIO for Linux. Ottawa Linux Symposium, 2005
|
||||
http://www.kernel.org/doc/ols/2005/ols2005v2-pages-43-56.pdf
|
||||
https://www.kernel.org/doc/ols/2005/ols2005v2-pages-43-56.pdf
|
||||
|
@ -93,4 +93,4 @@ Thermal management on Nouveau is new and may not work on all cards. If you have
|
||||
inquiries, please ping mupuf on IRC (#nouveau, freenode).
|
||||
|
||||
Bug reports should be filled on Freedesktop's bug tracker. Please follow
|
||||
http://nouveau.freedesktop.org/wiki/Bugs
|
||||
https://nouveau.freedesktop.org/wiki/Bugs
|
||||
|
@ -318,6 +318,6 @@ linux-usb Mailing List Archives:
|
||||
https://lore.kernel.org/linux-usb/
|
||||
|
||||
Programming Guide for Linux USB Device Drivers:
|
||||
http://lmu.web.psi.ch/docu/manuals/software_manuals/linux_sl/usb_linux_programming_guide.pdf
|
||||
https://lmu.web.psi.ch/docu/manuals/software_manuals/linux_sl/usb_linux_programming_guide.pdf
|
||||
|
||||
USB Home Page: http://www.usb.org
|
||||
USB Home Page: https://www.usb.org
|
||||
|
Loading…
Reference in New Issue
Block a user