Fix broken references for Documentation/*
Subsystems (59)
cover Fix broken references for Documentation/*
This patch series is against next-20200317. It fixes all references to files under Documentation/* that were moved, renamed or removed.
After this patch series, this script:
./scripts/documentation-file-ref-check
Doesn't complain about any broken reference.
Mauro Carvalho Chehab (12):
MAINTAINERS: dt: update display/allwinner file entry
MAINTAINERS: dt: update etnaviv file reference
MAINTAINERS: drop an old reference to stm32 pwm timers doc
docs: dt: fix references to m_can.txt file
docs: dt: fix references to ap806-system-controller.txt
docs: dt: fix a broken reference to input.yaml
docs: dt: fix broken reference to phy-cadence-torrent.yaml
docs: fix broken references to text files
docs: fix broken references for ReST files that moved around
docs: dt: display/ti: fix typos at the devicetree/ directory name
docs: filesystems: fix renamed references
docs: kernel-parameters.txt: remove reference for removed Intel MPX
Documentation/ABI/stable/sysfs-devices-node | 2 +- Documentation/ABI/testing/procfs-smaps_rollup | 2 +- Documentation/admin-guide/cpu-load.rst | 2 +- .../admin-guide/kernel-parameters.txt | 11 ++-- Documentation/admin-guide/nfs/nfsroot.rst | 2 +- .../bindings/arm/freescale/fsl,scu.txt | 2 +- .../bindings/display/ti/ti,am65x-dss.yaml | 2 +- .../bindings/display/ti/ti,j721e-dss.yaml | 2 +- .../bindings/display/ti/ti,k2g-dss.yaml | 2 +- .../devicetree/bindings/gpio/gpio-mvebu.txt | 2 +- .../devicetree/bindings/net/can/tcan4x5x.txt | 2 +- .../bindings/phy/ti,phy-j721e-wiz.yaml | 2 +- .../bindings/thermal/armada-thermal.txt | 2 +- .../doc-guide/maintainer-profile.rst | 2 +- .../driver-api/driver-model/device.rst | 4 +- .../driver-api/driver-model/overview.rst | 2 +- Documentation/filesystems/dax.txt | 2 +- Documentation/filesystems/dnotify.txt | 2 +- .../filesystems/ramfs-rootfs-initramfs.rst | 2 +- Documentation/filesystems/sysfs.rst | 2 +- Documentation/memory-barriers.txt | 2 +- .../powerpc/firmware-assisted-dump.rst | 2 +- Documentation/process/adding-syscalls.rst | 2 +- Documentation/process/submit-checklist.rst | 2 +- .../it_IT/process/adding-syscalls.rst | 2 +- .../it_IT/process/submit-checklist.rst | 2 +- .../translations/ko_KR/memory-barriers.txt | 2 +- .../translations/zh_CN/filesystems/sysfs.txt | 8 +-- .../zh_CN/process/submit-checklist.rst | 2 +- Documentation/virt/kvm/arm/pvtime.rst | 2 +- Documentation/virt/kvm/devices/vcpu.rst | 2 +- Documentation/virt/kvm/hypercalls.rst | 4 +- Documentation/virt/kvm/mmu.rst | 2 +- Documentation/virt/kvm/review-checklist.rst | 2 +- MAINTAINERS | 61 +++++++++---------- Next/merge.log | 12 ++-- arch/powerpc/include/uapi/asm/kvm_para.h | 2 +- arch/x86/kvm/mmu/mmu.c | 2 +- drivers/base/core.c | 2 +- .../allwinner/sun8i-ce/sun8i-ce-cipher.c | 2 +- .../crypto/allwinner/sun8i-ce/sun8i-ce-core.c | 2 +- .../allwinner/sun8i-ss/sun8i-ss-cipher.c | 2 +- .../crypto/allwinner/sun8i-ss/sun8i-ss-core.c | 2 +- drivers/gpu/drm/Kconfig | 2 +- drivers/gpu/drm/drm_ioctl.c | 2 +- drivers/gpu/drm/msm/disp/dpu1/dpu_kms.h | 2 +- drivers/hwtracing/coresight/Kconfig | 2 +- drivers/media/v4l2-core/v4l2-fwnode.c | 2 +- fs/Kconfig | 2 +- fs/Kconfig.binfmt | 2 +- fs/adfs/Kconfig | 2 +- fs/affs/Kconfig | 2 +- fs/afs/Kconfig | 6 +- fs/bfs/Kconfig | 2 +- fs/cramfs/Kconfig | 2 +- fs/ecryptfs/Kconfig | 2 +- fs/fat/Kconfig | 8 +-- fs/fuse/Kconfig | 2 +- fs/fuse/dev.c | 2 +- fs/hfs/Kconfig | 2 +- fs/hpfs/Kconfig | 2 +- fs/isofs/Kconfig | 2 +- fs/namespace.c | 2 +- fs/notify/inotify/Kconfig | 2 +- fs/ntfs/Kconfig | 2 +- fs/ocfs2/Kconfig | 2 +- fs/overlayfs/Kconfig | 6 +- fs/proc/Kconfig | 4 +- fs/romfs/Kconfig | 2 +- fs/sysfs/dir.c | 2 +- fs/sysfs/file.c | 2 +- fs/sysfs/mount.c | 2 +- fs/sysfs/symlink.c | 2 +- fs/sysv/Kconfig | 2 +- fs/udf/Kconfig | 2 +- include/linux/kobject.h | 2 +- include/linux/kobject_ns.h | 2 +- include/linux/mm.h | 4 +- include/linux/relay.h | 2 +- include/linux/sysfs.h | 2 +- include/uapi/linux/ethtool_netlink.h | 2 +- include/uapi/linux/kvm.h | 4 +- include/uapi/rdma/rdma_user_ioctl_cmds.h | 2 +- kernel/relay.c | 2 +- lib/kobject.c | 4 +- mm/gup.c | 12 ++-- tools/include/uapi/linux/kvm.h | 4 +- virt/kvm/arm/vgic/vgic-mmio-v3.c | 2 +- virt/kvm/arm/vgic/vgic.h | 4 +- 89 files changed, 151 insertions(+), 151 deletions(-)
Signature · 1 line
2.24.1
PATCH 4/12 docs: dt: fix references to m_can.txt file
This file was converted to json and renamed. Update its references accordingly.
--- Documentation/devicetree/bindings/net/can/tcan4x5x.txt | 2 +- MAINTAINERS | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
Documentation/devicetree/bindings/net/can/tcan4x5x.txt +1 -1
@@ -14,7 +14,7 @@ Required properties: the interrupt. - interrupts: interrupt specification for data-ready. -See Documentation/devicetree/bindings/net/can/m_can.txt for additional +See Documentation/devicetree/bindings/net/can/bosch,m_can.yaml for additional required property details. Optional properties:
MAINTAINERS +1 -1
@@ -10327,7 +10327,7 @@ M: Dan Murphy <[email protected]> M: Sriram Dash <[email protected]> L: [email protected] S: Maintained -F: Documentation/devicetree/bindings/net/can/m_can.txt +F: Documentation/devicetree/bindings/net/can/bosch,m_can.yaml F: drivers/net/can/m_can/m_can.c F: drivers/net/can/m_can/m_can.h F: drivers/net/can/m_can/m_can_platform.c
Signature · 1 line
2.24.1
PATCH 5/12 docs: dt: fix references to ap806-system-controller.txt
In reply to Mauro Carvalho Chehabap806-system-controller.txt was renamed to ap80x-system-controller.txt.
Update its references accordingly.
--- Documentation/devicetree/bindings/gpio/gpio-mvebu.txt | 2 +- Documentation/devicetree/bindings/thermal/armada-thermal.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
Documentation/devicetree/bindings/gpio/gpio-mvebu.txt +1 -1
@@ -14,7 +14,7 @@ Required properties: "marvell,armada-8k-gpio" should be used for the Armada 7K and 8K SoCs (either from AP or CP), see - Documentation/devicetree/bindings/arm/marvell/ap806-system-controller.txt + Documentation/devicetree/bindings/arm/marvell/ap80x-system-controller.txt for specific details about the offset property. - reg: Address and length of the register set for the device. Only one
Documentation/devicetree/bindings/thermal/armada-thermal.txt +1 -1
@@ -12,7 +12,7 @@ Required properties: Note: these bindings are deprecated for AP806/CP110 and should instead follow the rules described in: -Documentation/devicetree/bindings/arm/marvell/ap806-system-controller.txt +Documentation/devicetree/bindings/arm/marvell/ap80x-system-controller.txt Documentation/devicetree/bindings/arm/marvell/cp110-system-controller.txt - reg: Device's register space.
Signature · 1 line
2.24.1
PATCH 8/12 docs: fix broken references to text files
In reply to Mauro Carvalho ChehabSeveral references got broken due to txt to ReST conversion.
Several of them can be automatically fixed with:
scripts/documentation-file-ref-check --fix
--- Documentation/admin-guide/kernel-parameters.txt | 2 +- Documentation/memory-barriers.txt | 2 +- Documentation/process/submit-checklist.rst | 2 +- .../translations/it_IT/process/submit-checklist.rst | 2 +- Documentation/translations/ko_KR/memory-barriers.txt | 2 +- .../translations/zh_CN/filesystems/sysfs.txt | 2 +- .../translations/zh_CN/process/submit-checklist.rst | 2 +- Documentation/virt/kvm/arm/pvtime.rst | 2 +- Documentation/virt/kvm/devices/vcpu.rst | 2 +- Documentation/virt/kvm/hypercalls.rst | 4 ++-- arch/powerpc/include/uapi/asm/kvm_para.h | 2 +- drivers/gpu/drm/Kconfig | 2 +- drivers/gpu/drm/drm_ioctl.c | 2 +- drivers/hwtracing/coresight/Kconfig | 2 +- fs/fat/Kconfig | 8 ++++---- fs/fuse/Kconfig | 2 +- fs/fuse/dev.c | 2 +- fs/overlayfs/Kconfig | 6 +++--- include/linux/mm.h | 4 ++-- include/uapi/linux/ethtool_netlink.h | 2 +- include/uapi/rdma/rdma_user_ioctl_cmds.h | 2 +- mm/gup.c | 12 ++++++------ virt/kvm/arm/vgic/vgic-mmio-v3.c | 2 +- virt/kvm/arm/vgic/vgic.h | 4 ++-- 24 files changed, 37 insertions(+), 37 deletions(-)
Documentation/admin-guide/kernel-parameters.txt +1 -1
@@ -960,7 +960,7 @@ edid/1680x1050.bin, or edid/1920x1080.bin is given and no file with the same name exists. Details and instructions how to build your own EDID data are - available in Documentation/driver-api/edid.rst. An EDID + available in Documentation/admin-guide/edid.rst. An EDID data set will only be used for a particular connector, if its name and a colon are prepended to the EDID name. Each connector may use a unique EDID data
Documentation/memory-barriers.txt +1 -1
@@ -620,7 +620,7 @@ because the CPUs that the Linux kernel supports don't do writes until they are certain (1) that the write will actually happen, (2) of the location of the write, and (3) of the value to be written. But please carefully read the "CONTROL DEPENDENCIES" section and the -Documentation/RCU/rcu_dereference.txt file: The compiler can and does +Documentation/RCU/rcu_dereference.rst file: The compiler can and does break dependencies in a great many highly creative ways. CPU 1 CPU 2
Documentation/process/submit-checklist.rst +1 -1
@@ -107,7 +107,7 @@ and elsewhere regarding submitting Linux kernel patches. and why. 26) If any ioctl's are added by the patch, then also update - ``Documentation/ioctl/ioctl-number.rst``. + ``Documentation/userspace-api/ioctl/ioctl-number.rst``. 27) If your modified source code depends on or uses any of the kernel APIs or features that are related to the following ``Kconfig`` symbols,
Documentation/translations/it_IT/process/submit-checklist.rst +1 -1
@@ -117,7 +117,7 @@ sottomissione delle patch, in particolare sorgenti che ne spieghi la logica: cosa fanno e perché. 25) Se la patch aggiunge nuove chiamate ioctl, allora aggiornate - ``Documentation/ioctl/ioctl-number.rst``. + ``Documentation/userspace-api/ioctl/ioctl-number.rst``. 26) Se il codice che avete modificato dipende o usa una qualsiasi interfaccia o funzionalità del kernel che è associata a uno dei seguenti simboli
Documentation/translations/ko_KR/memory-barriers.txt +1 -1
@@ -641,7 +641,7 @@ P 는 짝수 번호 캐시 라인에 저장되어 있고, 변수 B 는 홀수 리눅스 커널이 지원하는 CPU 들은 (1) 쓰기가 정말로 일어날지, (2) 쓰기가 어디에 이루어질지, 그리고 (3) 쓰여질 값을 확실히 알기 전까지는 쓰기를 수행하지 않기 때문입니다. 하지만 "컨트롤 의존성" 섹션과 -Documentation/RCU/rcu_dereference.txt 파일을 주의 깊게 읽어 주시기 바랍니다: +Documentation/RCU/rcu_dereference.rst 파일을 주의 깊게 읽어 주시기 바랍니다: 컴파일러는 매우 창의적인 많은 방법으로 종속성을 깰 수 있습니다. CPU 1 CPU 2
Documentation/translations/zh_CN/filesystems/sysfs.txt +1 -1
@@ -281,7 +281,7 @@ drivers/ 包含了每个已为特定总线上的设备而挂载的驱动程序 假定驱动没有跨越多个总线类型)。 fs/ 包含了一个为文件系统设立的目录。现在每个想要导出属性的文件系统必须 -在 fs/ 下创建自己的层次结构(参见Documentation/filesystems/fuse.txt)。 +在 fs/ 下创建自己的层次结构(参见Documentation/filesystems/fuse.rst)。 dev/ 包含两个子目录: char/ 和 block/。在这两个子目录中,有以 <major>:<minor> 格式命名的符号链接。这些符号链接指向 sysfs 目录
Documentation/translations/zh_CN/process/submit-checklist.rst +1 -1
@@ -97,7 +97,7 @@ Linux内核补丁提交清单 24) 所有内存屏障例如 ``barrier()``, ``rmb()``, ``wmb()`` 都需要源代码中的注 释来解释它们正在执行的操作及其原因的逻辑。 -25) 如果补丁添加了任何ioctl,那么也要更新 ``Documentation/ioctl/ioctl-number.rst`` +25) 如果补丁添加了任何ioctl,那么也要更新 ``Documentation/userspace-api/ioctl/ioctl-number.rst`` 26) 如果修改后的源代码依赖或使用与以下 ``Kconfig`` 符号相关的任何内核API或 功能,则在禁用相关 ``Kconfig`` 符号和/或 ``=m`` (如果该选项可用)的情况
Documentation/virt/kvm/arm/pvtime.rst +1 -1
@@ -76,5 +76,5 @@ It is advisable that one or more 64k pages are set aside for the purpose of these structures and not used for other purposes, this enables the guest to map the region using 64k pages and avoids conflicting attributes with other memory. -For the user space interface see Documentation/virt/kvm/devices/vcpu.txt +For the user space interface see Documentation/virt/kvm/devices/vcpu.rst section "3. GROUP: KVM_ARM_VCPU_PVTIME_CTRL".
Documentation/virt/kvm/devices/vcpu.rst +1 -1
@@ -110,5 +110,5 @@ Returns: Specifies the base address of the stolen time structure for this VCPU. The base address must be 64 byte aligned and exist within a valid guest memory -region. See Documentation/virt/kvm/arm/pvtime.txt for more information +region. See Documentation/virt/kvm/arm/pvtime.rst for more information including the layout of the stolen time structure.
Documentation/virt/kvm/hypercalls.rst +2 -2
@@ -22,7 +22,7 @@ S390: number in R1. For further information on the S390 diagnose call as supported by KVM, - refer to Documentation/virt/kvm/s390-diag.txt. + refer to Documentation/virt/kvm/s390-diag.rst. PowerPC: It uses R3-R10 and hypercall number in R11. R4-R11 are used as output registers.
@@ -30,7 +30,7 @@ PowerPC: KVM hypercalls uses 4 byte opcode, that are patched with 'hypercall-instructions' property inside the device tree's /hypervisor node. - For more information refer to Documentation/virt/kvm/ppc-pv.txt + For more information refer to Documentation/virt/kvm/ppc-pv.rst MIPS: KVM hypercalls use the HYPCALL instruction with code 0 and the hypercall
arch/powerpc/include/uapi/asm/kvm_para.h +1 -1
@@ -31,7 +31,7 @@* Struct fields are always 32 or 64 bit aligned, depending on them being 32 * or 64 bit wide respectively. * -* See Documentation/virt/kvm/ppc-pv.txt +* See Documentation/virt/kvm/ppc-pv.rst */ struct kvm_vcpu_arch_shared {__u64 scratch1;
drivers/gpu/drm/Kconfig +1 -1
@@ -161,7 +161,7 @@ config DRM_LOAD_EDID_FIRMWARE monitor are unable to provide appropriate EDID data. Since this feature is provided as a workaround for broken hardware, the default case is N. Details and instructions how to build your own - EDID data are given in Documentation/driver-api/edid.rst. + EDID data are given in Documentation/admin-guide/edid.rst. config DRM_DP_CEC bool "Enable DisplayPort CEC-Tunneling-over-AUX HDMI support"
drivers/gpu/drm/drm_ioctl.c +1 -1
@@ -741,7 +741,7 @@ static const struct drm_ioctl_desc drm_ioctls[] = {* }; * * Please make sure that you follow all the best practices from -* ``Documentation/ioctl/botching-up-ioctls.rst``. Note that drm_ioctl() +* ``Documentation/process/botching-up-ioctls.rst``. Note that drm_ioctl() * automatically zero-extends structures, hence make sure you can add more stuff * at the end, i.e. don't put a variable sized array there. *
drivers/hwtracing/coresight/Kconfig +1 -1
@@ -107,7 +107,7 @@ config CORESIGHT_CPU_DEBUG can quickly get to know program counter (PC), secure state, exception level, etc. Before use debugging functionality, platform needs to ensure the clock domain and power domain are enabled - properly, please refer Documentation/trace/coresight-cpu-debug.rst + properly, please refer Documentation/trace/coresight/coresight-cpu-debug.rst for detailed description and the example for usage. config CORESIGHT_CTI
fs/fat/Kconfig +4 -4
@@ -69,7 +69,7 @@ config VFAT_FS The VFAT support enlarges your kernel by about 10 KB and it only works if you said Y to the "DOS FAT fs support" above. Please read - the file <file:Documentation/filesystems/vfat.txt> for details. If + the file <file:Documentation/filesystems/vfat.rst> for details. If unsure, say Y. To compile this as a module, choose M here: the module will be called
@@ -82,7 +82,7 @@ config FAT_DEFAULT_CODEPAGE help This option should be set to the codepage of your FAT filesystems. It can be overridden with the "codepage" mount option. - See <file:Documentation/filesystems/vfat.txt> for more information. + See <file:Documentation/filesystems/vfat.rst> for more information. config FAT_DEFAULT_IOCHARSET string "Default iocharset for FAT"
@@ -96,7 +96,7 @@ config FAT_DEFAULT_IOCHARSET Note that "utf8" is not recommended for FAT filesystems. If unsure, you shouldn't set "utf8" here - select the next option instead if you would like to use UTF-8 encoded file names by default. - See <file:Documentation/filesystems/vfat.txt> for more information. + See <file:Documentation/filesystems/vfat.rst> for more information. Enable any character sets you need in File Systems/Native Language Support.
@@ -114,4 +114,4 @@ config FAT_DEFAULT_UTF8 Say Y if you use UTF-8 encoding for file names, N otherwise. - See <file:Documentation/filesystems/vfat.txt> for more information. + See <file:Documentation/filesystems/vfat.rst> for more information.
fs/fuse/Kconfig +1 -1
@@ -12,7 +12,7 @@ config FUSE_FS although chances are your distribution already has that library installed if you've installed the "fuse" package itself. - See <file:Documentation/filesystems/fuse.txt> for more information. + See <file:Documentation/filesystems/fuse.rst> for more information. See <file:Documentation/Changes> for needed library/utility version. If you want to develop a userspace FS, or if you want to use
fs/fuse/dev.c +1 -1
@@ -2081,7 +2081,7 @@ static void end_polls(struct fuse_conn *fc)* The same effect is usually achievable through killing the filesystem daemon * and all users of the filesystem. The exception is the combination of an * asynchronous request and the tricky deadlock (see -* Documentation/filesystems/fuse.txt). +* Documentation/filesystems/fuse.rst). * * Aborting requests under I/O goes as follows: 1: Separate out unlocked * requests, they should be finished off immediately. Locked requests will be
fs/overlayfs/Kconfig +3 -3
@@ -9,7 +9,7 @@ config OVERLAY_FS 'lower' filesystem is either hidden or, in the case of directories, merged with the 'upper' object. - For more information see Documentation/filesystems/overlayfs.txt + For more information see Documentation/filesystems/overlayfs.rst config OVERLAY_FS_REDIRECT_DIR bool "Overlayfs: turn on redirect directory feature by default"
@@ -38,7 +38,7 @@ config OVERLAY_FS_REDIRECT_ALWAYS_FOLLOW If backward compatibility is not an issue, then it is safe and recommended to say N here. - For more information, see Documentation/filesystems/overlayfs.txt + For more information, see Documentation/filesystems/overlayfs.rst If unsure, say Y.
@@ -103,7 +103,7 @@ config OVERLAY_FS_XINO_AUTO If compatibility with applications that expect 32bit inodes is not an issue, then it is safe and recommended to say Y here. - For more information, see Documentation/filesystems/overlayfs.txt + For more information, see Documentation/filesystems/overlayfs.rst If unsure, say N.
include/linux/mm.h +2 -2
@@ -1219,7 +1219,7 @@ void unpin_user_pages(struct page **pages, unsigned long npages);* used to track the pincount (instead using of the GUP_PIN_COUNTING_BIAS * scheme). * -* For more information, please see Documentation/vm/pin_user_pages.rst. +* For more information, please see Documentation/core-api/pin_user_pages.rst. * * @page: pointer to page to be queried. * @Return: True, if it is likely that the page has been "dma-pinned".
@@ -2854,7 +2854,7 @@ struct page *follow_page(struct vm_area_struct *vma, unsigned long address,* releasing pages: get_user_pages*() pages must be released via put_page(), * while pin_user_pages*() pages must be released via unpin_user_page(). * -* Please see Documentation/vm/pin_user_pages.rst for more information. +* Please see Documentation/core-api/pin_user_pages.rst for more information. */ static inline int vm_fault_to_errno (vm_fault_t vm_fault,int foll_flags)
include/uapi/linux/ethtool_netlink.h +1 -1
@@ -2,7 +2,7 @@/* * include/uapi/linux/ethtool_netlink.h - netlink interface for ethtool * -* See Documentation/networking/ethtool-netlink.txt in kernel source tree for +* See Documentation/networking/ethtool-netlink.rst in kernel source tree for * doucumentation of the interface. */
include/uapi/rdma/rdma_user_ioctl_cmds.h +1 -1
@@ -36,7 +36,7 @@#include <linux/types.h> #include <linux/ioctl.h> -/* Documentation/ioctl/ioctl-number.rst */ +/* Documentation/userspace-api/ioctl/ioctl-number.rst */ #define RDMA_IOCTL_MAGIC 0x1b#define RDMA_VERBS_IOCTL \ _IOWR(RDMA_IOCTL_MAGIC, 1, struct ib_uverbs_ioctl_hdr)
mm/gup.c +6 -6
@@ -2832,9 +2832,9 @@ EXPORT_SYMBOL_GPL(get_user_pages_fast);* the arguments here are identical. * * FOLL_PIN means that the pages must be released via unpin_user_page(). Please -* see Documentation/vm/pin_user_pages.rst for further details. +* see Documentation/core-api/pin_user_pages.rst for further details. * -* This is intended for Case 1 (DIO) in Documentation/vm/pin_user_pages.rst. It +* This is intended for Case 1 (DIO) in Documentation/core-api/pin_user_pages.rst. It * is NOT intended for Case 2 (RDMA: long-term pins). */ int pin_user_pages_fast(unsigned long start, int nr_pages,
@@ -2872,9 +2872,9 @@ EXPORT_SYMBOL_GPL(pin_user_pages_fast);* the arguments here are identical. * * FOLL_PIN means that the pages must be released via unpin_user_page(). Please -* see Documentation/vm/pin_user_pages.rst for details. +* see Documentation/core-api/pin_user_pages.rst for details. * -* This is intended for Case 1 (DIO) in Documentation/vm/pin_user_pages.rst. It +* This is intended for Case 1 (DIO) in Documentation/core-api/pin_user_pages.rst. It * is NOT intended for Case 2 (RDMA: long-term pins). */ long pin_user_pages_remote(struct task_struct *tsk, struct mm_struct *mm,
@@ -2908,9 +2908,9 @@ EXPORT_SYMBOL(pin_user_pages_remote);* FOLL_PIN is set. * * FOLL_PIN means that the pages must be released via unpin_user_page(). Please -* see Documentation/vm/pin_user_pages.rst for details. +* see Documentation/core-api/pin_user_pages.rst for details. * -* This is intended for Case 1 (DIO) in Documentation/vm/pin_user_pages.rst. It +* This is intended for Case 1 (DIO) in Documentation/core-api/pin_user_pages.rst. It * is NOT intended for Case 2 (RDMA: long-term pins). */ long pin_user_pages(unsigned long start, unsigned long nr_pages,
virt/kvm/arm/vgic/vgic-mmio-v3.c +1 -1
@@ -300,7 +300,7 @@ static unsigned long vgic_v3_uaccess_read_pending(struct kvm_vcpu *vcpu,* pending state of interrupt is latched in pending_latch variable. * Userspace will save and restore pending state and line_level * separately. -* Refer to Documentation/virt/kvm/devices/arm-vgic-v3.txt +* Refer to Documentation/virt/kvm/devices/arm-vgic-v3.rst * for handling of ISPENDR and ICPENDR. */ for (i =0 ; i < len *8 ; i++) {
virt/kvm/arm/vgic/vgic.h +2 -2
@@ -42,7 +42,7 @@ VGIC_AFFINITY_LEVEL(val, 3))/* -* As per Documentation/virt/kvm/devices/arm-vgic-v3.txt, +* As per Documentation/virt/kvm/devices/arm-vgic-v3.rst, * below macros are defined for CPUREG encoding. */ #define KVM_REG_ARM_VGIC_SYSREG_OP0_MASK 0x000000000000c000
@@ -63,7 +63,7 @@ KVM_REG_ARM_VGIC_SYSREG_OP2_MASK)/* -* As per Documentation/virt/kvm/devices/arm-vgic-its.txt, +* As per Documentation/virt/kvm/devices/arm-vgic-its.rst, * below macros are defined for ITS table entry encoding. */ #define KVM_ITS_CTE_VALID_SHIFT 63
Signature · 1 line
2.24.1
PATCH 11/12 docs: filesystems: fix renamed references
In reply to Mauro Carvalho ChehabSome filesystem references got broken by a previous patch series I submitted. Address those.
--- Documentation/ABI/stable/sysfs-devices-node | 2 +- Documentation/ABI/testing/procfs-smaps_rollup | 2 +- Documentation/admin-guide/cpu-load.rst | 2 +- .../admin-guide/kernel-parameters.txt | 2 +- Documentation/admin-guide/nfs/nfsroot.rst | 2 +- .../driver-api/driver-model/device.rst | 4 +- .../driver-api/driver-model/overview.rst | 2 +- Documentation/filesystems/dax.txt | 2 +- Documentation/filesystems/dnotify.txt | 2 +- .../filesystems/ramfs-rootfs-initramfs.rst | 2 +- Documentation/filesystems/sysfs.rst | 2 +- .../powerpc/firmware-assisted-dump.rst | 2 +- Documentation/process/adding-syscalls.rst | 2 +- .../it_IT/process/adding-syscalls.rst | 2 +- .../translations/zh_CN/filesystems/sysfs.txt | 6 +-- MAINTAINERS | 54 +++++++++---------- Next/merge.log | 12 ++--- drivers/base/core.c | 2 +- drivers/gpu/drm/msm/disp/dpu1/dpu_kms.h | 2 +- fs/Kconfig | 2 +- fs/Kconfig.binfmt | 2 +- fs/adfs/Kconfig | 2 +- fs/affs/Kconfig | 2 +- fs/afs/Kconfig | 6 +-- fs/bfs/Kconfig | 2 +- fs/cramfs/Kconfig | 2 +- fs/ecryptfs/Kconfig | 2 +- fs/hfs/Kconfig | 2 +- fs/hpfs/Kconfig | 2 +- fs/isofs/Kconfig | 2 +- fs/namespace.c | 2 +- fs/notify/inotify/Kconfig | 2 +- fs/ntfs/Kconfig | 2 +- fs/ocfs2/Kconfig | 2 +- fs/proc/Kconfig | 4 +- fs/romfs/Kconfig | 2 +- fs/sysfs/dir.c | 2 +- fs/sysfs/file.c | 2 +- fs/sysfs/mount.c | 2 +- fs/sysfs/symlink.c | 2 +- fs/sysv/Kconfig | 2 +- fs/udf/Kconfig | 2 +- include/linux/kobject.h | 2 +- include/linux/kobject_ns.h | 2 +- include/linux/relay.h | 2 +- include/linux/sysfs.h | 2 +- kernel/relay.c | 2 +- lib/kobject.c | 4 +- 48 files changed, 86 insertions(+), 86 deletions(-)
Documentation/ABI/stable/sysfs-devices-node +1 -1
@@ -54,7 +54,7 @@ Date: October 2002 Contact: Linux Memory Management list <[email protected]> Description: Provides information about the node's distribution and memory - utilization. Similar to /proc/meminfo, see Documentation/filesystems/proc.txt + utilization. Similar to /proc/meminfo, see Documentation/filesystems/proc.rst What: /sys/devices/system/node/nodeX/numastat Date: October 2002
Documentation/ABI/testing/procfs-smaps_rollup +1 -1
@@ -11,7 +11,7 @@ Description: Additionally, the fields Pss_Anon, Pss_File and Pss_Shmem are not present in /proc/pid/smaps. These fields represent the sum of the Pss field of each type (anon, file, shmem). - For more details, see Documentation/filesystems/proc.txt + For more details, see Documentation/filesystems/proc.rst and the procfs man page. Typical output looks like this:
Documentation/admin-guide/cpu-load.rst +1 -1
@@ -105,7 +105,7 @@ References ---------- - https://urldefense.com/v3/__http://lkml.org/lkml/2007/2/12/6__;!!GqivPVa7Brio!OI3KpYBfoX4Xrzl92Wp7PRPh-eDjGLZV5Q_QY-Vj_SecpBlSAKFhhX4rR6WGcYMo8vDqWQ$ -- Documentation/filesystems/proc.txt (1.8) +- Documentation/filesystems/proc.rst (1.8) Thanks
Documentation/admin-guide/kernel-parameters.txt +1 -1
@@ -683,7 +683,7 @@ coredump_filter= [KNL] Change the default value for /proc/<pid>/coredump_filter. - See also Documentation/filesystems/proc.txt. + See also Documentation/filesystems/proc.rst. coresight_cpu_debug.enable [ARM,ARM64]
Documentation/admin-guide/nfs/nfsroot.rst +1 -1
@@ -18,7 +18,7 @@ Mounting the root filesystem via NFS (nfsroot) In order to use a diskless system, such as an X-terminal or printer server for example, it is necessary for the root filesystem to be present on a non-disk device. This may be an initramfs (see -Documentation/filesystems/ramfs-rootfs-initramfs.txt), a ramdisk (see +Documentation/filesystems/ramfs-rootfs-initramfs.rst), a ramdisk (see Documentation/admin-guide/initrd.rst) or a filesystem mounted via NFS. The following text describes on how to use NFS for the root filesystem. For the rest of this text 'client' means the diskless system, and 'server' means the NFS
Documentation/driver-api/driver-model/device.rst +2 -2
@@ -50,10 +50,10 @@ Attributes Attributes of devices can be exported by a device driver through sysfs. -Please see Documentation/filesystems/sysfs.txt for more information +Please see Documentation/filesystems/sysfs.rst for more information on how sysfs works. -As explained in Documentation/kobject.txt, device attributes must be +As explained in Documentation/core-api/kobject.rst, device attributes must be created before the KOBJ_ADD uevent is generated. The only way to realize that is by defining an attribute group.
Documentation/driver-api/driver-model/overview.rst +1 -1
@@ -121,4 +121,4 @@ device-specific data or tunable interfaces. More information about the sysfs directory layout can be found in the other documents in this directory and in the file -Documentation/filesystems/sysfs.txt. +Documentation/filesystems/sysfs.rst.
Documentation/filesystems/dax.txt +1 -1
@@ -74,7 +74,7 @@ are zeroed out and converted to written extents before being returned to avoid exposure of uninitialized data through mmap. These filesystems may be used for inspiration: -- ext2: see Documentation/filesystems/ext2.txt +- ext2: see Documentation/filesystems/ext2.rst - ext4: see Documentation/filesystems/ext4/ - xfs: see Documentation/admin-guide/xfs.rst
Documentation/filesystems/dnotify.txt +1 -1
@@ -67,4 +67,4 @@ See tools/testing/selftests/filesystems/dnotify_test.c for an example. NOTE ---- Beginning with Linux 2.6.13, dnotify has been replaced by inotify. -See Documentation/filesystems/inotify.txt for more information on it. +See Documentation/filesystems/inotify.rst for more information on it.
Documentation/filesystems/ramfs-rootfs-initramfs.rst +1 -1
@@ -71,7 +71,7 @@ be allowed write access to a ramfs mount. A ramfs derivative called tmpfs was created to add size limits, and the ability to write the data to swap space. Normal users can be allowed write access to -tmpfs mounts. See Documentation/filesystems/tmpfs.txt for more information. +tmpfs mounts. See Documentation/filesystems/tmpfs.rst for more information. What is rootfs? ---------------
Documentation/filesystems/sysfs.rst +1 -1
@@ -20,7 +20,7 @@ a means to export kernel data structures, their attributes, and the linkages between them to userspace. sysfs is tied inherently to the kobject infrastructure. Please read -Documentation/kobject.txt for more information concerning the kobject +Documentation/core-api/kobject.rst for more information concerning the kobject interface.
Documentation/powerpc/firmware-assisted-dump.rst +1 -1
@@ -344,7 +344,7 @@ Here is the list of files under powerpc debugfs: NOTE: - Please refer to Documentation/filesystems/debugfs.txt on + Please refer to Documentation/filesystems/debugfs.rst on how to mount the debugfs filesystem.
Documentation/process/adding-syscalls.rst +1 -1
@@ -33,7 +33,7 @@ interface. to a somewhat opaque API. - If you're just exposing runtime system information, a new node in sysfs - (see ``Documentation/filesystems/sysfs.txt``) or the ``/proc`` filesystem may + (see ``Documentation/filesystems/sysfs.rst``) or the ``/proc`` filesystem may be more appropriate. However, access to these mechanisms requires that the relevant filesystem is mounted, which might not always be the case (e.g. in a namespaced/sandboxed/chrooted environment). Avoid adding any API to
Documentation/translations/it_IT/process/adding-syscalls.rst +1 -1
@@ -39,7 +39,7 @@ vostra interfaccia. un qualche modo opaca. - Se dovete esporre solo delle informazioni sul sistema, un nuovo nodo in - sysfs (vedere ``Documentation/filesystems/sysfs.txt``) o + sysfs (vedere ``Documentation/filesystems/sysfs.rst``) o in procfs potrebbe essere sufficiente. Tuttavia, l'accesso a questi meccanismi richiede che il filesystem sia montato, il che potrebbe non essere sempre vero (per esempio, in ambienti come namespace/sandbox/chroot).
Documentation/translations/zh_CN/filesystems/sysfs.txt +3 -3
@@ -1,4 +1,4 @@ -Chinese translated version of Documentation/filesystems/sysfs.txt +Chinese translated version of Documentation/filesystems/sysfs.rst If you have any comment or update to the content, please contact the original document maintainer directly. However, if you have a problem
@@ -10,7 +10,7 @@ Maintainer: Patrick Mochel <[email protected]> Mike Murphy <[email protected]> Chinese maintainer: Fu Wei <[email protected]> --------------------------------------------------------------------- -Documentation/filesystems/sysfs.txt ????? +Documentation/filesystems/sysfs.rst ????? ?????????????????????????????????? ??????????????????????????????????
@@ -40,7 +40,7 @@ sysfs ??????? ramfs ??????????????? ??????????????????????????? sysfs ??? kobject ????????????? -Documentation/kobject.txt ????????? kobject ??? +Documentation/core-api/kobject.rst ????????? kobject ??? ???
MAINTAINERS +27 -27
209 lines not on this page · raw message
Next/merge.log +6 -6
@@ -2510,9 +2510,9 @@ Auto-merging Documentation/kbuild/index.rst CONFLICT (content): Merge conflict in Documentation/kbuild/index.rst Auto-merging Documentation/filesystems/zonefs.rst CONFLICT (content): Merge conflict in Documentation/filesystems/zonefs.rst -Removing Documentation/filesystems/omfs.txt +Removing Documentation/filesystems/omfs.rst Removing Documentation/filesystems/nfs/nfs41-server.txt -Removing Documentation/filesystems/isofs.txt +Removing Documentation/filesystems/isofs.rst Auto-merging Documentation/filesystems/debugfs.rst Removing Documentation/debugging-modules.txt Auto-merging Documentation/admin-guide/kernel-parameters.txt
@@ -2580,7 +2580,7 @@ $ git diff -M --stat --summary HEAD^.. Documentation/filesystems/index.rst | 45 + .../filesystems/{inotify.txt => inotify.rst} | 33 +- Documentation/filesystems/isofs.rst | 64 + - Documentation/filesystems/isofs.txt | 48 - + Documentation/filesystems/isofs.rst | 48 - Documentation/filesystems/nfs/index.rst | 13 + .../nfs/{knfsd-stats.txt => knfsd-stats.rst} | 17 +- Documentation/filesystems/nfs/nfs41-server.rst | 256 ++++
@@ -2593,7 +2593,7 @@ $ git diff -M --stat --summary HEAD^.. ...ne-filecheck.txt => ocfs2-online-filecheck.rst} | 45 +- Documentation/filesystems/{ocfs2.txt => ocfs2.rst} | 31 +- Documentation/filesystems/omfs.rst | 112 ++ - Documentation/filesystems/omfs.txt | 106 -- + Documentation/filesystems/omfs.rst | 106 -- .../filesystems/{orangefs.txt => orangefs.rst} | 187 ++- Documentation/filesystems/{proc.txt => proc.rst} | 1544 +++++++++++--------- Documentation/filesystems/{qnx6.txt => qnx6.rst} | 22 +
@@ -2681,7 +2681,7 @@ $ git diff -M --stat --summary HEAD^.. rename Documentation/filesystems/{hpfs.txt => hpfs.rst} (66%) rename Documentation/filesystems/{inotify.txt => inotify.rst} (83%) create mode 100644 Documentation/filesystems/isofs.rst - delete mode 100644 Documentation/filesystems/isofs.txt + delete mode 100644 Documentation/filesystems/isofs.rst create mode 100644 Documentation/filesystems/nfs/index.rst rename Documentation/filesystems/nfs/{knfsd-stats.txt => knfsd-stats.rst} (95%) create mode 100644 Documentation/filesystems/nfs/nfs41-server.rst
@@ -2694,7 +2694,7 @@ $ git diff -M --stat --summary HEAD^.. rename Documentation/filesystems/{ocfs2-online-filecheck.txt => ocfs2-online-filecheck.rst} (77%) rename Documentation/filesystems/{ocfs2.txt => ocfs2.rst} (88%) create mode 100644 Documentation/filesystems/omfs.rst - delete mode 100644 Documentation/filesystems/omfs.txt + delete mode 100644 Documentation/filesystems/omfs.rst rename Documentation/filesystems/{orangefs.txt => orangefs.rst} (83%) rename Documentation/filesystems/{proc.txt => proc.rst} (65%) rename Documentation/filesystems/{qnx6.txt => qnx6.rst} (98%)
drivers/base/core.c +1 -1
@@ -1374,7 +1374,7 @@ static void device_release(struct kobject *kobj)else if (dev->class && dev->class->dev_release) dev->class->dev_release (dev);else -WARN (1 ,KERN_ERR "Device '%s' does not have a release() function, it is broken and must be fixed. See Documentation/kobject.txt.\n" , +WARN (1 ,KERN_ERR "Device '%s' does not have a release() function, it is broken and must be fixed. See Documentation/core-api/kobject.rst.\n" ,dev_name (dev));kfree (p); }
drivers/gpu/drm/msm/disp/dpu1/dpu_kms.h +1 -1
@@ -144,7 +144,7 @@ struct vsync_info {* * Main debugfs documentation is located at, * -* Documentation/filesystems/debugfs.txt +* Documentation/filesystems/debugfs.rst * * @dpu_debugfs_setup_regset32: Initialize data for dpu_debugfs_create_regset32 * @dpu_debugfs_create_regset32: Create 32-bit register dump file
fs/Kconfig +1 -1
@@ -166,7 +166,7 @@ config TMPFS space. If you unmount a tmpfs instance, everything stored therein is lost. - See <file:Documentation/filesystems/tmpfs.txt> for details. + See <file:Documentation/filesystems/tmpfs.rst> for details. config TMPFS_POSIX_ACL bool "Tmpfs POSIX Access Control Lists"
fs/Kconfig.binfmt +1 -1
@@ -72,7 +72,7 @@ config CORE_DUMP_DEFAULT_ELF_HEADERS The core dump behavior can be controlled per process using the /proc/PID/coredump_filter pseudo-file; this setting is - inherited. See Documentation/filesystems/proc.txt for details. + inherited. See Documentation/filesystems/proc.rst for details. This config option changes the default setting of coredump_filter seen at boot time. If unsure, say Y.
fs/adfs/Kconfig +1 -1
@@ -12,7 +12,7 @@ config ADFS_FS The ADFS partition should be the first partition (i.e., /dev/[hs]d?1) on each of your drives. Please read the file - <file:Documentation/filesystems/adfs.txt> for further details. + <file:Documentation/filesystems/adfs.rst> for further details. To compile this code as a module, choose M here: the module will be called adfs.
fs/affs/Kconfig +1 -1
@@ -9,7 +9,7 @@ config AFFS_FS FFS partition on your hard drive. Amiga floppies however cannot be read with this driver due to an incompatibility of the floppy controller used in an Amiga and the standard floppy controller in - PCs and workstations. Read <file:Documentation/filesystems/affs.txt> + PCs and workstations. Read <file:Documentation/filesystems/affs.rst> and <file:fs/affs/Changes>. With this driver you can also mount disk files used by Bernd
fs/afs/Kconfig +3 -3
@@ -8,7 +8,7 @@ config AFS_FS If you say Y here, you will get an experimental Andrew File System driver. It currently only supports unsecured read-only AFS access. - See <file:Documentation/filesystems/afs.txt> for more information. + See <file:Documentation/filesystems/afs.rst> for more information. If unsure, say N.
@@ -18,7 +18,7 @@ config AFS_DEBUG help Say Y here to make runtime controllable debugging messages appear. - See <file:Documentation/filesystems/afs.txt> for more information. + See <file:Documentation/filesystems/afs.rst> for more information. If unsure, say N.
@@ -37,6 +37,6 @@ config AFS_DEBUG_CURSOR the dmesg log if the server rotation algorithm fails to successfully contact a server. - See <file:Documentation/filesystems/afs.txt> for more information. + See <file:Documentation/filesystems/afs.rst> for more information. If unsure, say N.
fs/bfs/Kconfig +1 -1
@@ -11,7 +11,7 @@ config BFS_FS on your /stand slice from within Linux. You then also need to say Y to "UnixWare slices support", below. More information about the BFS file system is contained in the file - <file:Documentation/filesystems/bfs.txt>. + <file:Documentation/filesystems/bfs.rst>. If you don't know what this is about, say N.
fs/cramfs/Kconfig +1 -1
@@ -9,7 +9,7 @@ config CRAMFS limited to 256MB file systems (with 16MB files), and doesn't support 16/32 bits uid/gid, hard links and timestamps. - See <file:Documentation/filesystems/cramfs.txt> and + See <file:Documentation/filesystems/cramfs.rst> and <file:fs/cramfs/README> for further information. To compile this as a module, choose M here: the module will be called
fs/ecryptfs/Kconfig +1 -1
@@ -7,7 +7,7 @@ config ECRYPT_FS select CRYPTO_MD5 help Encrypted filesystem that operates on the VFS layer. See - <file:Documentation/filesystems/ecryptfs.txt> to learn more about + <file:Documentation/filesystems/ecryptfs.rst> to learn more about eCryptfs. Userspace components are required and can be obtained from <https://urldefense.com/v3/__http://ecryptfs.sf.net__;!!GqivPVa7Brio!OI3KpYBfoX4Xrzl92Wp7PRPh-eDjGLZV5Q_QY-Vj_SecpBlSAKFhhX4rR6WGcYP1tPctCg$ >.
fs/hfs/Kconfig +1 -1
@@ -6,7 +6,7 @@ config HFS_FS help If you say Y here, you will be able to mount Macintosh-formatted floppy disks and hard drive partitions with full read-write access. - Please read <file:Documentation/filesystems/hfs.txt> to learn about + Please read <file:Documentation/filesystems/hfs.rst> to learn about the available mount options. To compile this file system support as a module, choose M here: the
fs/hpfs/Kconfig +1 -1
@@ -9,7 +9,7 @@ config HPFS_FS write files to an OS/2 HPFS partition on your hard drive. OS/2 floppies however are in regular MSDOS format, so you don't need this option in order to be able to read them. Read - <file:Documentation/filesystems/hpfs.txt>. + <file:Documentation/filesystems/hpfs.rst>. To compile this file system support as a module, choose M here: the module will be called hpfs. If unsure, say N.
fs/isofs/Kconfig +1 -1
@@ -8,7 +8,7 @@ config ISO9660_FS long Unix filenames and symbolic links are also supported by this driver. If you have a CD-ROM drive and want to do more with it than just listen to audio CDs and watch its LEDs, say Y (and read - <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO, + <file:Documentation/filesystems/isofs.rst> and the CD-ROM-HOWTO, available from <https://urldefense.com/v3/__http://www.tldp.org/docs.html*howto__;Iw!!GqivPVa7Brio!OI3KpYBfoX4Xrzl92Wp7PRPh-eDjGLZV5Q_QY-Vj_SecpBlSAKFhhX4rR6WGcYNRCwVbEQ$ >), thereby enlarging your kernel by about 27 KB; otherwise say N.
fs/namespace.c +1 -1
@@ -3592,7 +3592,7 @@ EXPORT_SYMBOL(path_is_under);* file system may be mounted on put_old. After all, new_root is a mountpoint. * * Also, the current root cannot be on the 'rootfs' (initial ramfs) filesystem. -* See Documentation/filesystems/ramfs-rootfs-initramfs.txt for alternatives +* See Documentation/filesystems/ramfs-rootfs-initramfs.rst for alternatives * in this situation. * * Notes:
fs/notify/inotify/Kconfig +1 -1
@@ -12,6 +12,6 @@ config INOTIFY_USER new features including multiple file events, one-shot support, and unmount notification. - For more information, see <file:Documentation/filesystems/inotify.txt> + For more information, see <file:Documentation/filesystems/inotify.rst> If unsure, say Y.
fs/ntfs/Kconfig +1 -1
@@ -18,7 +18,7 @@ config NTFS_FS the Linux 2.4 kernel series is separately available as a patch from the project web site. - For more information see <file:Documentation/filesystems/ntfs.txt> + For more information see <file:Documentation/filesystems/ntfs.rst> and <https://urldefense.com/v3/__http://www.linux-ntfs.org/__;!!GqivPVa7Brio!OI3KpYBfoX4Xrzl92Wp7PRPh-eDjGLZV5Q_QY-Vj_SecpBlSAKFhhX4rR6WGcYNwmipoXw$ >. To compile this file system support as a module, choose M here: the
fs/ocfs2/Kconfig +1 -1
@@ -21,7 +21,7 @@ config OCFS2_FS OCFS2 mailing lists: http://oss.oracle.com/projects/ocfs2/mailman/ For more information on OCFS2, see the file - <file:Documentation/filesystems/ocfs2.txt>. + <file:Documentation/filesystems/ocfs2.rst>. config OCFS2_FS_O2CB tristate "O2CB Kernelspace Clustering"
fs/proc/Kconfig +2 -2
@@ -23,7 +23,7 @@ config PROC_FS /proc" or the equivalent line in /etc/fstab does the job. The /proc file system is explained in the file - <file:Documentation/filesystems/proc.txt> and on the proc(5) manpage + <file:Documentation/filesystems/proc.rst> and on the proc(5) manpage ("man 5 proc"). This option will enlarge your kernel by about 67 KB. Several
@@ -95,7 +95,7 @@ config PROC_CHILDREN default n help Provides a fast way to retrieve first level children pids of a task. See - <file:Documentation/filesystems/proc.txt> for more information. + <file:Documentation/filesystems/proc.rst> for more information. Say Y if you are running any user-space software which takes benefit from this interface. For example, rkt is such a piece of software.
fs/romfs/Kconfig +1 -1
@@ -6,7 +6,7 @@ config ROMFS_FS This is a very small read-only file system mainly intended for initial ram disks of installation disks, but it could be used for other read-only media as well. Read - <file:Documentation/filesystems/romfs.txt> for details. + <file:Documentation/filesystems/romfs.rst> for details. To compile this file system support as a module, choose M here: the module will be called romfs. Note that the file system of your
fs/sysfs/dir.c +1 -1
@@ -6,7 +6,7 @@* Copyright (c) 2007 SUSE Linux Products GmbH * Copyright (c) 2007 Tejun Heo <[email protected]> * -* Please see Documentation/filesystems/sysfs.txt for more information. +* Please see Documentation/filesystems/sysfs.rst for more information. */ #define pr_fmt (fmt) "sysfs: " fmt
fs/sysfs/file.c +1 -1
@@ -6,7 +6,7 @@* Copyright (c) 2007 SUSE Linux Products GmbH * Copyright (c) 2007 Tejun Heo <[email protected]> * -* Please see Documentation/filesystems/sysfs.txt for more information. +* Please see Documentation/filesystems/sysfs.rst for more information. */ #include <linux/module.h>
fs/sysfs/mount.c +1 -1
@@ -6,7 +6,7 @@* Copyright (c) 2007 SUSE Linux Products GmbH * Copyright (c) 2007 Tejun Heo <[email protected]> * -* Please see Documentation/filesystems/sysfs.txt for more information. +* Please see Documentation/filesystems/sysfs.rst for more information. */ #include <linux/fs.h>
fs/sysfs/symlink.c +1 -1
@@ -6,7 +6,7 @@* Copyright (c) 2007 SUSE Linux Products GmbH * Copyright (c) 2007 Tejun Heo <[email protected]> * -* Please see Documentation/filesystems/sysfs.txt for more information. +* Please see Documentation/filesystems/sysfs.rst for more information. */ #include <linux/fs.h>
fs/sysv/Kconfig +1 -1
@@ -28,7 +28,7 @@ config SYSV_FS tar" or preferably "info tar"). Note also that this option has nothing whatsoever to do with the option "System V IPC". Read about the System V file system in - <file:Documentation/filesystems/sysv-fs.txt>. + <file:Documentation/filesystems/sysv-fs.rst>. Saying Y here will enlarge your kernel by about 27 KB. To compile this as a module, choose M here: the module will be called
fs/udf/Kconfig +1 -1
@@ -9,7 +9,7 @@ config UDF_FS compatible with standard unix file systems, it is also suitable for removable USB disks. Say Y if you intend to mount DVD discs or CDRW's written in packet mode, or if you want to use UDF for removable USB - disks. Please read <file:Documentation/filesystems/udf.txt>. + disks. Please read <file:Documentation/filesystems/udf.rst>. To compile this file system support as a module, choose M here: the module will be called udf.
include/linux/kobject.h +1 -1
@@ -7,7 +7,7 @@* Copyright (c) 2006-2008 Greg Kroah-Hartman <[email protected]> * Copyright (c) 2006-2008 Novell Inc. * -* Please read Documentation/kobject.txt before using the kobject +* Please read Documentation/core-api/kobject.rst before using the kobject * interface, ESPECIALLY the parts about reference counts and object * destructors. */
include/linux/kobject_ns.h +1 -1
@@ -8,7 +8,7 @@* * Split from kobject.h by David Howells (dhowells at redhat.com) * -* Please read Documentation/kobject.txt before using the kobject +* Please read Documentation/core-api/kobject.rst before using the kobject * interface, ESPECIALLY the parts about reference counts and object * destructors. */
include/linux/relay.h +1 -1
@@ -141,7 +141,7 @@ struct rchan_callbacks* cause relay_open() to create a single global buffer rather * than the default set of per-cpu buffers. * -* See Documentation/filesystems/relay.txt for more info. +* See Documentation/filesystems/relay.rst for more info. */ struct dentry *(*create_buf_file)(const char *filename, struct dentry *parent,
include/linux/sysfs.h +1 -1
@@ -7,7 +7,7 @@* Copyright (c) 2007 SUSE Linux Products GmbH * Copyright (c) 2007 Tejun Heo <[email protected]> * -* Please see Documentation/filesystems/sysfs.txt for more information. +* Please see Documentation/filesystems/sysfs.rst for more information. */ #ifndef _SYSFS_H_
kernel/relay.c +1 -1
@@ -1,7 +1,7 @@/* * Public API and common code for kernel->userspace relay file support. * -* See Documentation/filesystems/relay.txt for an overview. +* See Documentation/filesystems/relay.rst for an overview. * * Copyright (C) 2002-2005 - Tom Zanussi (zanussi at us.ibm.com), IBM Corp * Copyright (C) 1999-2005 - Karim Yaghmour (karim at opersys.com)
lib/kobject.c +2 -2
@@ -6,7 +6,7 @@* Copyright (c) 2006-2007 Greg Kroah-Hartman <[email protected]> * Copyright (c) 2006-2007 Novell Inc. * -* Please see the file Documentation/kobject.txt for critical information +* Please see the file Documentation/core-api/kobject.rst for critical information * about using the kobject interface. */
@@ -670,7 +670,7 @@ static void kobject_cleanup(struct kobject *kobj) kobject_name(kobj), kobj, __func__, kobj->parent);if (t && !t->release) -pr_debug ("kobject: '%s' (%p): does not have a release() function, it is broken and must be fixed. See Documentation/kobject.txt.\n" , +pr_debug ("kobject: '%s' (%p): does not have a release() function, it is broken and must be fixed. See Documentation/core-api/kobject.rst.\n" ,kobject_name (kobj), kobj);/* send "remove" if the caller did not do it but sent "add" */
Signature · 1 line
2.24.1
PATCH 3/12 MAINTAINERS: drop an old reference to stm32 pwm timers doc
In reply to Mauro Carvalho ChehabThe DT files for pwm were merged and converted to json. The new reference is already at the maintainers file, so just drop the obsoleted one.
--- MAINTAINERS | 1 - 1 file changed, 1 deletion(-)
MAINTAINERS +0 -1
@@ -16055,7 +16055,6 @@ F: drivers/pwm/pwm-stm32* F: include/linux/*/stm32-*tim* F: Documentation/ABI/testing/*timer-stm32 F: Documentation/devicetree/bindings/*/*stm32-*timer* -F: Documentation/devicetree/bindings/pwm/pwm-stm32* STMMAC ETHERNET DRIVER M: Giuseppe Cavallaro <[email protected]>
Signature · 1 line
2.24.1
PATCH 10/12 docs: dt: display/ti: fix typos at the devicetree/ directory name
In reply to Mauro Carvalho ChehabThe name of the devicetree directory is wrong on those three TI bindings:
--- Documentation/devicetree/bindings/display/ti/ti,am65x-dss.yaml | 2 +- Documentation/devicetree/bindings/display/ti/ti,j721e-dss.yaml | 2 +- Documentation/devicetree/bindings/display/ti/ti,k2g-dss.yaml | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)
Documentation/devicetree/bindings/display/ti/ti,am65x-dss.yaml +1 -1
@@ -65,7 +65,7 @@ properties: ports: type: object description: - Ports as described in Documentation/devictree/bindings/graph.txt + Ports as described in Documentation/devicetree/bindings/graph.txt properties: "#address-cells": const: 1
Documentation/devicetree/bindings/display/ti/ti,j721e-dss.yaml +1 -1
@@ -98,7 +98,7 @@ properties: ports: type: object description: - Ports as described in Documentation/devictree/bindings/graph.txt + Ports as described in Documentation/devicetree/bindings/graph.txt properties: "#address-cells": const: 1
Documentation/devicetree/bindings/display/ti/ti,k2g-dss.yaml +1 -1
@@ -56,7 +56,7 @@ properties: port: type: object description: - Port as described in Documentation/devictree/bindings/graph.txt. + Port as described in Documentation/devicetree/bindings/graph.txt. The DSS DPI output port node max-memory-bandwidth:
Signature · 6 lines
2.24.1 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
PATCH 9/12 docs: fix broken references for ReST files that moved around
In reply to Mauro Carvalho ChehabSome broken references happened due to shifting files around and ReST renames. Those can't be auto-fixed by the script, so let's fix them manually.
--- Documentation/doc-guide/maintainer-profile.rst | 2 +- Documentation/virt/kvm/mmu.rst | 2 +- Documentation/virt/kvm/review-checklist.rst | 2 +- arch/x86/kvm/mmu/mmu.c | 2 +- drivers/crypto/allwinner/sun8i-ce/sun8i-ce-cipher.c | 2 +- drivers/crypto/allwinner/sun8i-ce/sun8i-ce-core.c | 2 +- drivers/crypto/allwinner/sun8i-ss/sun8i-ss-cipher.c | 2 +- drivers/crypto/allwinner/sun8i-ss/sun8i-ss-core.c | 2 +- drivers/media/v4l2-core/v4l2-fwnode.c | 2 +- include/uapi/linux/kvm.h | 4 ++-- tools/include/uapi/linux/kvm.h | 4 ++-- 11 files changed, 13 insertions(+), 13 deletions(-)
Documentation/doc-guide/maintainer-profile.rst +1 -1
@@ -6,7 +6,7 @@ Documentation subsystem maintainer entry profile The documentation "subsystem" is the central coordinating point for the kernel's documentation and associated infrastructure. It covers the hierarchy under Documentation/ (with the exception of -Documentation/device-tree), various utilities under scripts/ and, at least +Documentation/devicetree), various utilities under scripts/ and, at least some of the time, LICENSES/. It's worth noting, though, that the boundaries of this subsystem are rather
Documentation/virt/kvm/mmu.rst +1 -1
@@ -319,7 +319,7 @@ Handling a page fault is performed as follows: - If both P bit and R/W bit of error code are set, this could possibly be handled as a "fast page fault" (fixed without taking the MMU lock). See - the description in Documentation/virt/kvm/locking.txt. + the description in Documentation/virt/kvm/locking.rst. - if needed, walk the guest page tables to determine the guest translation (gva->gpa or ngpa->gpa)
Documentation/virt/kvm/review-checklist.rst +1 -1
@@ -10,7 +10,7 @@ Review checklist for kvm patches 2. Patches should be against kvm.git master branch. 3. If the patch introduces or modifies a new userspace API: - - the API must be documented in Documentation/virt/kvm/api.txt + - the API must be documented in Documentation/virt/kvm/api.rst - the API must be discoverable using KVM_CHECK_EXTENSION 4. New state must include support for save/restore.
arch/x86/kvm/mmu/mmu.c +1 -1
@@ -3586,7 +3586,7 @@ static bool fast_page_fault(struct kvm_vcpu *vcpu, gpa_t cr2_or_gpa,/* * Currently, fast page fault only works for direct mapping * since the gfn is not stable for indirect shadow page. See -* Documentation/virt/kvm/locking.txt to get more detail. +* Documentation/virt/kvm/locking.rst to get more detail. */ fault_handled = fast_pf_fix_direct_spte(vcpu, sp, iterator.sptep, spte,
drivers/crypto/allwinner/sun8i-ce/sun8i-ce-cipher.c +1 -1
@@ -8,7 +8,7 @@* This file add support for AES cipher with 128,192,256 bits keysize in * CBC and ECB mode. * -* You could find a link for the datasheet in Documentation/arm/sunxi/README +* You could find a link for the datasheet in Documentation/arm/sunxi.rst */ #include <linux/crypto.h>
drivers/crypto/allwinner/sun8i-ce/sun8i-ce-core.c +1 -1
@@ -7,7 +7,7 @@* * Core file which registers crypto algorithms supported by the CryptoEngine. * -* You could find a link for the datasheet in Documentation/arm/sunxi/README +* You could find a link for the datasheet in Documentation/arm/sunxi.rst */ #include <linux/clk.h> #include <linux/crypto.h>
drivers/crypto/allwinner/sun8i-ss/sun8i-ss-cipher.c +1 -1
@@ -8,7 +8,7 @@* This file add support for AES cipher with 128,192,256 bits keysize in * CBC and ECB mode. * -* You could find a link for the datasheet in Documentation/arm/sunxi/README +* You could find a link for the datasheet in Documentation/arm/sunxi.rst */ #include <linux/crypto.h>
drivers/crypto/allwinner/sun8i-ss/sun8i-ss-core.c +1 -1
@@ -7,7 +7,7 @@* * Core file which registers crypto algorithms supported by the SecuritySystem * -* You could find a link for the datasheet in Documentation/arm/sunxi/README +* You could find a link for the datasheet in Documentation/arm/sunxi.rst */ #include <linux/clk.h> #include <linux/crypto.h>
drivers/media/v4l2-core/v4l2-fwnode.c +1 -1
@@ -980,7 +980,7 @@ static int v4l2_fwnode_reference_parse(struct device *dev,* * THIS EXAMPLE EXISTS MERELY TO DOCUMENT THIS FUNCTION. DO NOT USE IT AS A * REFERENCE IN HOW ACPI TABLES SHOULD BE WRITTEN!! See documentation under -* Documentation/acpi/dsd instead and especially graph.txt, +* Documentation/firmware-guide/acpi/dsd/ instead and especially graph.txt, * data-node-references.txt and leds.txt . * * Scope (\_SB.PCI0.I2C2)
include/uapi/linux/kvm.h +2 -2
@@ -116,7 +116,7 @@ struct kvm_irq_level {* ACPI gsi notion of irq. * For IA-64 (APIC model) IOAPIC0: irq 0-23; IOAPIC1: irq 24-47.. * For X86 (standard AT mode) PIC0/1: irq 0-15. IOAPIC0: 0-23.. -* For ARM: See Documentation/virt/kvm/api.txt +* For ARM: See Documentation/virt/kvm/api.rst */ union {__u32 irq;
@@ -1106,7 +1106,7 @@ struct kvm_xen_hvm_config {* * KVM_IRQFD_FLAG_RESAMPLE indicates resamplefd is valid and specifies * the irqfd to operate in resampling mode for level triggered interrupt -* emulation. See Documentation/virt/kvm/api.txt. +* emulation. See Documentation/virt/kvm/api.rst. */ #define KVM_IRQFD_FLAG_RESAMPLE (1 << 1)
tools/include/uapi/linux/kvm.h +2 -2
@@ -116,7 +116,7 @@ struct kvm_irq_level {* ACPI gsi notion of irq. * For IA-64 (APIC model) IOAPIC0: irq 0-23; IOAPIC1: irq 24-47.. * For X86 (standard AT mode) PIC0/1: irq 0-15. IOAPIC0: 0-23.. -* For ARM: See Documentation/virt/kvm/api.txt +* For ARM: See Documentation/virt/kvm/api.rst */ union {__u32 irq;
@@ -1100,7 +1100,7 @@ struct kvm_xen_hvm_config {* * KVM_IRQFD_FLAG_RESAMPLE indicates resamplefd is valid and specifies * the irqfd to operate in resampling mode for level triggered interrupt -* emulation. See Documentation/virt/kvm/api.txt. +* emulation. See Documentation/virt/kvm/api.rst. */ #define KVM_IRQFD_FLAG_RESAMPLE (1 << 1)
Signature · 1 line
2.24.1
PATCH 2/12 MAINTAINERS: dt: update etnaviv file reference
In reply to Mauro Carvalho ChehabThe etnaviv file was converted to json and renamed.
Update its reference accordingly.
--- MAINTAINERS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
MAINTAINERS +1 -1
@@ -5768,7 +5768,7 @@ L: [email protected] S: Maintained F: drivers/gpu/drm/etnaviv/ F: include/uapi/drm/etnaviv_drm.h -F: Documentation/devicetree/bindings/display/etnaviv/ +F: Documentation/devicetree/bindings/gpu/vivante,gc.yaml DRM DRIVERS FOR ZTE ZX M: Shawn Guo <[email protected]>
Signature · 1 line
2.24.1
PATCH 1/12 MAINTAINERS: dt: update display/allwinner file entry
In reply to Mauro Carvalho ChehabChangeset f5a98bfe7b37 ("dt-bindings: display: Convert Allwinner display pipeline to schemas") split Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt
into several files. Yet, it kept the old place at MAINTAINERS.
Update it to point to the new place.
--- MAINTAINERS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
MAINTAINERS +1 -1
@@ -5552,7 +5552,7 @@ M: Chen-Yu Tsai <[email protected]> L: [email protected] S: Supported F: drivers/gpu/drm/sun4i/ -F: Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt +F: Documentation/devicetree/bindings/display/allwinner* T: git git://anongit.freedesktop.org/drm/drm-misc DRM DRIVER FOR ALLWINNER DE2 AND DE3 ENGINE
Signature · 1 line
2.24.1
PATCH 6/12 docs: dt: fix a broken reference to input.yaml
In reply to Mauro Carvalho ChehabThe old file was converted to yaml, but its reference was still pointing to the old one.
--- Documentation/devicetree/bindings/arm/freescale/fsl,scu.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/devicetree/bindings/arm/freescale/fsl,scu.txt +1 -1
@@ -164,7 +164,7 @@ Required properties: - compatible: should be: "fsl,imx8qxp-sc-key" followed by "fsl,imx-sc-key"; -- linux,keycodes: See Documentation/devicetree/bindings/input/keys.txt +- linux,keycodes: See Documentation/devicetree/bindings/input/input.yaml Thermal bindings based on SCU Message Protocol ------------------------------------------------------------
Signature · 1 line
2.24.1
PATCH 12/12 docs: kernel-parameters.txt: remove reference for removed Intel MPX
In reply to Mauro Carvalho ChehabThe Intel MPX support got removed on Kernel 5.6, but the kernel-parameters file still mentions it.
Update the text to document that this parameter is not needed anymore, as the Intel MPX will always be disabled now on (as its support got removed).
--- Documentation/admin-guide/kernel-parameters.txt | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)
Documentation/admin-guide/kernel-parameters.txt +4 -3
@@ -990,9 +990,10 @@ Documentation/admin-guide/dynamic-debug-howto.rst for details. - nompx [X86] Disables Intel Memory Protection Extensions. - See Documentation/x86/intel_mpx.rst for more - information about the feature. + nompx X86] Previously, disabled Intel Memory Protection + Extensions. + NOTE: It is now default, as the Intel MPX code + was removed in v5.6. nopku [X86] Disable Memory Protection Keys CPU feature found in some Intel CPUs.
Signature · 1 line
2.24.1
PATCH 7/12 docs: dt: fix broken reference to phy-cadence-torrent.yaml
In reply to Mauro Carvalho ChehabThis file was removed, and another file was added instead of it, on two separate commits.
Splitting a single logical change (doc conversion) on two patches is a bad thing, as it makes harder to discover what crap happened.
Anyway, this patch fixes the broken reference, making it pointing to the new location of the file.
--- Documentation/devicetree/bindings/phy/ti,phy-j721e-wiz.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/devicetree/bindings/phy/ti,phy-j721e-wiz.yaml +1 -1
@@ -146,7 +146,7 @@ patternProperties: bindings specified in Documentation/devicetree/bindings/phy/phy-cadence-sierra.txt Torrent SERDES should follow the bindings specified in - Documentation/devicetree/bindings/phy/phy-cadence-dp.txt + Documentation/devicetree/bindings/phy/phy-cadence-torrent.yaml required: - compatible
Signature · 1 line
2.24.1
Re: [PATCH 04/12] docs: dt: fix references to m_can.txt file
In reply to Mauro Carvalho ChehabQuoted 5 lines · Mauro Carvalho Chehab
This file was converted to json and renamed. Update its references accordingly.
Fixes 824674b59f72 ("dt-bindings: net: can: Convert M_CAN to json-schema")Signed-off-by Mauro Carvalho Chehab <[email protected]>
regards,
Marc
Signature · 4 lines
Pengutronix e.K. | Marc Kleine-Budde | Embedded Linux | https://www.pengutronix.de | Vertretung West/Dortmund | Phone: +49-231-2826-924 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
Re: [PATCH 08/12] docs: fix broken references to text files
In reply to Mauro Carvalho ChehabQuoted 20 lines · Mauro Carvalho Chehab
Several references got broken due to txt to ReST conversion.
Several of them can be automatically fixed with:
scripts/documentation-file-ref-check --fixSigned-off-by Mauro Carvalho Chehab <[email protected]>Documentation/admin-guide/kernel-parameters.txt | 2 +- Documentation/memory-barriers.txt | 2 +- Documentation/process/submit-checklist.rst | 2 +- .../translations/it_IT/process/submit-checklist.rst | 2 +- Documentation/translations/ko_KR/memory-barriers.txt | 2 +- .../translations/zh_CN/filesystems/sysfs.txt | 2 +- .../translations/zh_CN/process/submit-checklist.rst | 2 +- Documentation/virt/kvm/arm/pvtime.rst | 2 +- Documentation/virt/kvm/devices/vcpu.rst | 2 +- Documentation/virt/kvm/hypercalls.rst | 4 ++-- arch/powerpc/include/uapi/asm/kvm_para.h | 2 +- drivers/gpu/drm/Kconfig | 2 +- drivers/gpu/drm/drm_ioctl.c | 2 +-
Quoted 8 lines
drivers/hwtracing/coresight/Kconfig | 2 +- fs/fat/Kconfig | 8 ++++---- fs/fuse/Kconfig | 2 +- fs/fuse/dev.c | 2 +- fs/overlayfs/Kconfig | 6 +++--- include/linux/mm.h | 4 ++-- include/uapi/linux/ethtool_netlink.h | 2 +- include/uapi/rdma/rdma_user_ioctl_cmds.h | 2 +-
For the rdma files
Jason
Re: [PATCH 04/12] docs: dt: fix references to m_can.txt file
In reply to Marc Kleine-BuddeHello
Quoted 5 lines · Marc Kleine-Budde
Quoted 4 lines · Mauro Carvalho Chehab
This file was converted to json and renamed. Update its references accordingly.
Fixes 824674b59f72 ("dt-bindings: net: can: Convert M_CAN to json-schema")
I am trying to find out where the above commit was applied
I don't see it in can-next or linux-can. I need to update the tcan dt binding file as it was missed.
And I am not sure why the maintainers of these files were not CC'd on the conversion of this binding.
Dan
Re: [PATCH 10/12] docs: dt: display/ti: fix typos at the devicetree/ directory name
In reply to Mauro Carvalho ChehabQuoted 4 lines · Mauro Carvalho Chehab
The name of the devicetree directory is wrong on those three TI bindings:
Signed-off-by Mauro Carvalho Chehab <[email protected]>
Quoted 46 lines
--- Documentation/devicetree/bindings/display/ti/ti,am65x-dss.yaml | 2 +- Documentation/devicetree/bindings/display/ti/ti,j721e-dss.yaml | 2 +- Documentation/devicetree/bindings/display/ti/ti,k2g-dss.yaml | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)Documentation/devicetree/bindings/display/ti/ti,am65x-dss.yaml +1
-1@@ -65,7 +65,7 @@ properties: ports: type: object description: - Ports as described in Documentation/devictree/bindings/graph.txt + Ports as described in Documentation/devicetree/bindings/graph.txt properties: "#address-cells": const: 1Documentation/devicetree/bindings/display/ti/ti,j721e-dss.yaml +1
-1@@ -98,7 +98,7 @@ properties: ports: type: object description: - Ports as described in Documentation/devictree/bindings/graph.txt + Ports as described in Documentation/devicetree/bindings/graph.txt properties: "#address-cells": const: 1Documentation/devicetree/bindings/display/ti/ti,k2g-dss.yaml +1
-1@@ -56,7 +56,7 @@ properties: port: type: object description: - Port as described in Documentation/devictree/bindings/graph.txt. + Port as described in Documentation/devicetree/bindings/graph.txt. The DSS DPI output port node max-memory-bandwidth:
Signature · 6 lines
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH 05/12] docs: dt: fix references to ap806-system-controller.txt
In reply to Mauro Carvalho Chehabwt., 17 mar 2020 o 14:10 Mauro Carvalho Chehab
<[email protected]> napisał(a):
Quoted 39 lines
ap806-system-controller.txt was renamed to ap80x-system-controller.txt.
Update its references accordingly.
Fixes 2537831bbc19 ("dt-bindings: ap80x: replace AP806 with AP80x")Signed-off-by Mauro Carvalho Chehab <[email protected]>--- Documentation/devicetree/bindings/gpio/gpio-mvebu.txt | 2 +- Documentation/devicetree/bindings/thermal/armada-thermal.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)Documentation/devicetree/bindings/gpio/gpio-mvebu.txt +1
-1@@ -14,7 +14,7 @@ Required properties: "marvell,armada-8k-gpio" should be used for the Armada 7K and 8K SoCs (either from AP or CP), see - Documentation/devicetree/bindings/arm/marvell/ap806-system-controller.txt + Documentation/devicetree/bindings/arm/marvell/ap80x-system-controller.txt for specific details about the offset property. - reg: Address and length of the register set for the device. Only oneDocumentation/devicetree/bindings/thermal/armada-thermal.txt +1
-2@@ -12,7 +12,7 @@ Required properties: Note: these bindings are deprecated for AP806/CP110 and should instead follow the rules described in: -Documentation/devicetree/bindings/arm/marvell/ap806-system-controller.txt +Documentation/devicetree/bindings/arm/marvell/ap80x-system-controller.txt Documentation/devicetree/bindings/arm/marvell/cp110-system-controller.txt - reg: Device's register space. --
Quoted 2 lines
2.24.1
For GPIO:
Re: [PATCH 04/12] docs: dt: fix references to m_can.txt file
In reply to Dan MurphyQuoted 10 lines · Dan Murphy
Hello
Quoted 6 lines · Marc Kleine-Budde
Quoted 5 lines · Mauro Carvalho Chehab
This file was converted to json and renamed. Update its references accordingly.
Fixes 824674b59f72 ("dt-bindings: net: can: Convert M_CAN tojson-schema")
Quoted 7 lines
I am trying to find out where the above commit was applied
I don't see it in can-next or linux-can. I need to update the tcan dt binding file as it was missed.
And I am not sure why the maintainers of these files were not CC'd on the conversion of this binding.
It was merged in device-tree-next.
I have put in copy the people that get_maintainers provides to me. Sorry if I forgot someone.
Benjamin
Quoted 3 lines
Dan
Re: [PATCH 04/12] docs: dt: fix references to m_can.txt file
In reply to Dan MurphyEm Tue, 17 Mar 2020 08:29:45 -0500
Dan Murphy <[email protected]> escreveu:
Quoted 9 lines
Hello
Quoted 5 lines · Marc Kleine-Budde
Quoted 4 lines · Mauro Carvalho Chehab
This file was converted to json and renamed. Update its references accordingly.
Fixes 824674b59f72 ("dt-bindings: net: can: Convert M_CAN to json-schema")
Quoted 7 lines
I am trying to find out where the above commit was applied
I don't see it in can-next or linux-can. I need to update the tcan dt binding file as it was missed.
And I am not sure why the maintainers of these files were not CC'd on the conversion of this binding.
From Next/merge.log:
Merging devicetree/for-next (d047cd8a2760 scripts/dtc: Update to upstream version v1.6.0-2-g87a656ae5ff9)
$ git merge devicetree/for-next Removing scripts/dtc/libfdt/Makefile.libfdt Removing scripts/dtc/Makefile.dtc ... create mode 100644 Documentation/devicetree/bindings/net/can/bosch,m_can.yaml delete mode 100644 Documentation/devicetree/bindings/net/can/m_can.txt
It sounds that those came from DT for-next branch.
Thanks,
Mauro
Re: [PATCH 08/12] docs: fix broken references to text files
In reply to Mauro Carvalho ChehabQuoted 213 lines · Mauro Carvalho Chehab
Several references got broken due to txt to ReST conversion.
Several of them can be automatically fixed with:
scripts/documentation-file-ref-check --fixSigned-off-by Mauro Carvalho Chehab <[email protected]>--- Documentation/admin-guide/kernel-parameters.txt | 2 +- Documentation/memory-barriers.txt | 2 +- Documentation/process/submit-checklist.rst | 2 +- .../translations/it_IT/process/submit-checklist.rst | 2 +- Documentation/translations/ko_KR/memory-barriers.txt | 2 +- .../translations/zh_CN/filesystems/sysfs.txt | 2 +- .../translations/zh_CN/process/submit-checklist.rst | 2 +- Documentation/virt/kvm/arm/pvtime.rst | 2 +- Documentation/virt/kvm/devices/vcpu.rst | 2 +- Documentation/virt/kvm/hypercalls.rst | 4 ++-- arch/powerpc/include/uapi/asm/kvm_para.h | 2 +- drivers/gpu/drm/Kconfig | 2 +- drivers/gpu/drm/drm_ioctl.c | 2 +- drivers/hwtracing/coresight/Kconfig | 2 +- fs/fat/Kconfig | 8 ++++---- fs/fuse/Kconfig | 2 +- fs/fuse/dev.c | 2 +- fs/overlayfs/Kconfig | 6 +++--- include/linux/mm.h | 4 ++-- include/uapi/linux/ethtool_netlink.h | 2 +- include/uapi/rdma/rdma_user_ioctl_cmds.h | 2 +- mm/gup.c | 12 ++++++------ virt/kvm/arm/vgic/vgic-mmio-v3.c | 2 +- virt/kvm/arm/vgic/vgic.h | 4 ++-- 24 files changed, 37 insertions(+), 37 deletions(-)Documentation/admin-guide/kernel-parameters.txt +1
-1@@ -960,7 +960,7 @@ edid/1680x1050.bin, or edid/1920x1080.bin is given and no file with the same name exists. Details and instructions how to build your own EDID data are - available in Documentation/driver-api/edid.rst. An EDID + available in Documentation/admin-guide/edid.rst. An EDID data set will only be used for a particular connector, if its name and a colon are prepended to the EDID name. Each connector may use a unique EDID dataDocumentation/memory-barriers.txt +1
-1@@ -620,7 +620,7 @@ because the CPUs that the Linux kernel supports don't do writes until they are certain (1) that the write will actually happen, (2) of the location of the write, and (3) of the value to be written. But please carefully read the "CONTROL DEPENDENCIES" section and the -Documentation/RCU/rcu_dereference.txt file: The compiler can and does +Documentation/RCU/rcu_dereference.rst file: The compiler can and does break dependencies in a great many highly creative ways. CPU 1 CPU 2Documentation/process/submit-checklist.rst +1
-1@@ -107,7 +107,7 @@ and elsewhere regarding submitting Linux kernel patches. and why. 26) If any ioctl's are added by the patch, then also update - ``Documentation/ioctl/ioctl-number.rst``. + ``Documentation/userspace-api/ioctl/ioctl-number.rst``. 27) If your modified source code depends on or uses any of the kernel APIs or features that are related to the following ``Kconfig`` symbols,Documentation/translations/it_IT/process/submit-checklist.rst +1
-1@@ -117,7 +117,7 @@ sottomissione delle patch, in particolare sorgenti che ne spieghi la logica: cosa fanno e perché. 25) Se la patch aggiunge nuove chiamate ioctl, allora aggiornate - ``Documentation/ioctl/ioctl-number.rst``. + ``Documentation/userspace-api/ioctl/ioctl-number.rst``. 26) Se il codice che avete modificato dipende o usa una qualsiasi interfaccia o funzionalità del kernel che è associata a uno dei seguenti simboliDocumentation/translations/ko_KR/memory-barriers.txt +1
-1@@ -641,7 +641,7 @@ P 는 짝수 번호 캐시 라인에 저장되어 있고, 변수 B 는 홀수 리눅스 커널이 지원하는 CPU 들은 (1) 쓰기가 정말로 일어날지, (2) 쓰기가 어디에 이루어질지, 그리고 (3) 쓰여질 값을 확실히 알기 전까지는 쓰기를 수행하지 않기 때문입니다. 하지만 "컨트롤 의존성" 섹션과 -Documentation/RCU/rcu_dereference.txt 파일을 주의 깊게 읽어 주시기 바랍니다: +Documentation/RCU/rcu_dereference.rst 파일을 주의 깊게 읽어 주시기 바랍니다: 컴파일러는 매우 창의적인 많은 방법으로 종속성을 깰 수 있습니다. CPU 1 CPU 2Documentation/translations/zh_CN/filesystems/sysfs.txt +1
-1@@ -281,7 +281,7 @@ drivers/ 包含了每个已为特定总线上的设备而挂载的驱动程序 假定驱动没有跨越多个总线类型)。 fs/ 包含了一个为文件系统设立的目录。现在每个想要导出属性的文件系统必须 -在 fs/ 下创建自己的层次结构(参见Documentation/filesystems/fuse.txt)。 +在 fs/ 下创建自己的层次结构(参见Documentation/filesystems/fuse.rst)。 dev/ 包含两个子目录: char/ 和 block/。在这两个子目录中,有以 <major>:<minor> 格式命名的符号链接。这些符号链接指向 sysfs 目录Documentation/translations/zh_CN/process/submit-checklist.rst +1
-1@@ -97,7 +97,7 @@ Linux内核补丁提交清单 24) 所有内存屏障例如 ``barrier()``, ``rmb()``, ``wmb()`` 都需要源代码中的注 释来解释它们正在执行的操作及其原因的逻辑。 -25) 如果补丁添加了任何ioctl,那么也要更新 ``Documentation/ioctl/ioctl-number.rst`` +25) 如果补丁添加了任何ioctl,那么也要更新 ``Documentation/userspace-api/ioctl/ioctl-number.rst`` 26) 如果修改后的源代码依赖或使用与以下 ``Kconfig`` 符号相关的任何内核API或 功能,则在禁用相关 ``Kconfig`` 符号和/或 ``=m`` (如果该选项可用)的情况Documentation/virt/kvm/arm/pvtime.rst +1
-1@@ -76,5 +76,5 @@ It is advisable that one or more 64k pages are set aside for the purpose of these structures and not used for other purposes, this enables the guest to map the region using 64k pages and avoids conflicting attributes with other memory. -For the user space interface see Documentation/virt/kvm/devices/vcpu.txt +For the user space interface see Documentation/virt/kvm/devices/vcpu.rst section "3. GROUP: KVM_ARM_VCPU_PVTIME_CTRL".Documentation/virt/kvm/devices/vcpu.rst +1
-1@@ -110,5 +110,5 @@ Returns: Specifies the base address of the stolen time structure for this VCPU. The base address must be 64 byte aligned and exist within a valid guest memory -region. See Documentation/virt/kvm/arm/pvtime.txt for more information +region. See Documentation/virt/kvm/arm/pvtime.rst for more information including the layout of the stolen time structure.Documentation/virt/kvm/hypercalls.rst +2
-2@@ -22,7 +22,7 @@ S390: number in R1. For further information on the S390 diagnose call as supported by KVM, - refer to Documentation/virt/kvm/s390-diag.txt. + refer to Documentation/virt/kvm/s390-diag.rst. PowerPC: It uses R3-R10 and hypercall number in R11. R4-R11 are used as output registers.@@ -30,7 +30,7 @@ PowerPC: KVM hypercalls uses 4 byte opcode, that are patched with 'hypercall-instructions' property inside the device tree's /hypervisor node. - For more information refer to Documentation/virt/kvm/ppc-pv.txt + For more information refer to Documentation/virt/kvm/ppc-pv.rst MIPS: KVM hypercalls use the HYPCALL instruction with code 0 and the hypercallarch/powerpc/include/uapi/asm/kvm_para.h +1
-1@@ -31,7 +31,7 @@* Struct fields are always 32 or 64 bit aligned, depending on them being 32 * or 64 bit wide respectively. * -* See Documentation/virt/kvm/ppc-pv.txt +* See Documentation/virt/kvm/ppc-pv.rst */ struct kvm_vcpu_arch_shared {__u64 scratch1;drivers/gpu/drm/Kconfig +1
-1@@ -161,7 +161,7 @@ config DRM_LOAD_EDID_FIRMWARE monitor are unable to provide appropriate EDID data. Since this feature is provided as a workaround for broken hardware, the default case is N. Details and instructions how to build your own - EDID data are given in Documentation/driver-api/edid.rst. + EDID data are given in Documentation/admin-guide/edid.rst. config DRM_DP_CEC bool "Enable DisplayPort CEC-Tunneling-over-AUX HDMI support"drivers/gpu/drm/drm_ioctl.c +1
-1@@ -741,7 +741,7 @@ static const struct drm_ioctl_desc drm_ioctls[] = {* }; * * Please make sure that you follow all the best practices from -* ``Documentation/ioctl/botching-up-ioctls.rst``. Note that drm_ioctl() +* ``Documentation/process/botching-up-ioctls.rst``. Note that drm_ioctl() * automatically zero-extends structures, hence make sure you can add more stuff * at the end, i.e. don't put a variable sized array there. * drivers/hwtracing/coresight/Kconfig +0
-0
drivers/hwtracing/coresight/Kconfig config CORESIGHT_CPU_DEBUG · line 110
Quoted 5 lines
drivers/hwtracing/coresight/Kconfig +1
-1@@ -107,7 +107,7 @@ config CORESIGHT_CPU_DEBUG can quickly get to know program counter (PC), secure state, exception level, etc. Before use debugging functionality, platform needs to ensure the clock domain and power domain are enabled - properly, please refer Documentation/trace/coresight-cpu-debug.rst + properly, please refer Documentation/trace/coresight/coresight-cpu-debug.rst
Quoted 223 lines
drivers/hwtracing/coresight/Kconfig +0
-0for detailed description and the example for usage. config CORESIGHT_CTIfs/fat/Kconfig +4
-4@@ -69,7 +69,7 @@ config VFAT_FS The VFAT support enlarges your kernel by about 10 KB and it only works if you said Y to the "DOS FAT fs support" above. Please read - the file <file:Documentation/filesystems/vfat.txt> for details. If + the file <file:Documentation/filesystems/vfat.rst> for details. If unsure, say Y. To compile this as a module, choose M here: the module will be called@@ -82,7 +82,7 @@ config FAT_DEFAULT_CODEPAGE help This option should be set to the codepage of your FAT filesystems. It can be overridden with the "codepage" mount option. - See <file:Documentation/filesystems/vfat.txt> for more information. + See <file:Documentation/filesystems/vfat.rst> for more information. config FAT_DEFAULT_IOCHARSET string "Default iocharset for FAT"@@ -96,7 +96,7 @@ config FAT_DEFAULT_IOCHARSET Note that "utf8" is not recommended for FAT filesystems. If unsure, you shouldn't set "utf8" here - select the next option instead if you would like to use UTF-8 encoded file names by default. - See <file:Documentation/filesystems/vfat.txt> for more information. + See <file:Documentation/filesystems/vfat.rst> for more information. Enable any character sets you need in File Systems/Native Language Support.@@ -114,4 +114,4 @@ config FAT_DEFAULT_UTF8 Say Y if you use UTF-8 encoding for file names, N otherwise. - See <file:Documentation/filesystems/vfat.txt> for more information. + See <file:Documentation/filesystems/vfat.rst> for more information.fs/fuse/Kconfig +1
-1@@ -12,7 +12,7 @@ config FUSE_FS although chances are your distribution already has that library installed if you've installed the "fuse" package itself. - See <file:Documentation/filesystems/fuse.txt> for more information. + See <file:Documentation/filesystems/fuse.rst> for more information. See <file:Documentation/Changes> for needed library/utility version. If you want to develop a userspace FS, or if you want to usefs/fuse/dev.c +1
-1@@ -2081,7 +2081,7 @@ static void end_polls(struct fuse_conn *fc)* The same effect is usually achievable through killing the filesystem daemon * and all users of the filesystem. The exception is the combination of an * asynchronous request and the tricky deadlock (see -* Documentation/filesystems/fuse.txt). +* Documentation/filesystems/fuse.rst). * * Aborting requests under I/O goes as follows: 1: Separate out unlocked * requests, they should be finished off immediately. Locked requests will be fs/overlayfs/Kconfig +3
-3@@ -9,7 +9,7 @@ config OVERLAY_FS 'lower' filesystem is either hidden or, in the case of directories, merged with the 'upper' object. - For more information see Documentation/filesystems/overlayfs.txt + For more information see Documentation/filesystems/overlayfs.rst config OVERLAY_FS_REDIRECT_DIR bool "Overlayfs: turn on redirect directory feature by default"@@ -38,7 +38,7 @@ config OVERLAY_FS_REDIRECT_ALWAYS_FOLLOW If backward compatibility is not an issue, then it is safe and recommended to say N here. - For more information, see Documentation/filesystems/overlayfs.txt + For more information, see Documentation/filesystems/overlayfs.rst If unsure, say Y.@@ -103,7 +103,7 @@ config OVERLAY_FS_XINO_AUTO If compatibility with applications that expect 32bit inodes is not an issue, then it is safe and recommended to say Y here. - For more information, see Documentation/filesystems/overlayfs.txt + For more information, see Documentation/filesystems/overlayfs.rst If unsure, say N.include/linux/mm.h +2
-2@@ -1219,7 +1219,7 @@ void unpin_user_pages(struct page **pages, unsigned long npages);* used to track the pincount (instead using of the GUP_PIN_COUNTING_BIAS * scheme). * -* For more information, please see Documentation/vm/pin_user_pages.rst. +* For more information, please see Documentation/core-api/pin_user_pages.rst. * * @page: pointer to page to be queried. * @Return: True, if it is likely that the page has been "dma-pinned". @@ -2854,7 +2854,7 @@ struct page *follow_page(struct vm_area_struct *vma, unsigned long address,* releasing pages: get_user_pages*() pages must be released via put_page(), * while pin_user_pages*() pages must be released via unpin_user_page(). * -* Please see Documentation/vm/pin_user_pages.rst for more information. +* Please see Documentation/core-api/pin_user_pages.rst for more information. */ static inline int vm_fault_to_errno (vm_fault_t vm_fault,int foll_flags)include/uapi/linux/ethtool_netlink.h +1
-1@@ -2,7 +2,7 @@/* * include/uapi/linux/ethtool_netlink.h - netlink interface for ethtool * -* See Documentation/networking/ethtool-netlink.txt in kernel source tree for +* See Documentation/networking/ethtool-netlink.rst in kernel source tree for * doucumentation of the interface. */ include/uapi/rdma/rdma_user_ioctl_cmds.h +1
-1@@ -36,7 +36,7 @@#include <linux/types.h> #include <linux/ioctl.h> -/* Documentation/ioctl/ioctl-number.rst */ +/* Documentation/userspace-api/ioctl/ioctl-number.rst */ #define RDMA_IOCTL_MAGIC 0x1b#define RDMA_VERBS_IOCTL \ _IOWR(RDMA_IOCTL_MAGIC, 1, struct ib_uverbs_ioctl_hdr)mm/gup.c +6
-6@@ -2832,9 +2832,9 @@ EXPORT_SYMBOL_GPL(get_user_pages_fast);* the arguments here are identical. * * FOLL_PIN means that the pages must be released via unpin_user_page(). Please -* see Documentation/vm/pin_user_pages.rst for further details. +* see Documentation/core-api/pin_user_pages.rst for further details. * -* This is intended for Case 1 (DIO) in Documentation/vm/pin_user_pages.rst. It +* This is intended for Case 1 (DIO) in Documentation/core-api/pin_user_pages.rst. It * is NOT intended for Case 2 (RDMA: long-term pins). */ int pin_user_pages_fast(unsigned long start, int nr_pages,@@ -2872,9 +2872,9 @@ EXPORT_SYMBOL_GPL(pin_user_pages_fast);* the arguments here are identical. * * FOLL_PIN means that the pages must be released via unpin_user_page(). Please -* see Documentation/vm/pin_user_pages.rst for details. +* see Documentation/core-api/pin_user_pages.rst for details. * -* This is intended for Case 1 (DIO) in Documentation/vm/pin_user_pages.rst. It +* This is intended for Case 1 (DIO) in Documentation/core-api/pin_user_pages.rst. It * is NOT intended for Case 2 (RDMA: long-term pins). */ long pin_user_pages_remote(struct task_struct *tsk, struct mm_struct *mm,@@ -2908,9 +2908,9 @@ EXPORT_SYMBOL(pin_user_pages_remote);* FOLL_PIN is set. * * FOLL_PIN means that the pages must be released via unpin_user_page(). Please -* see Documentation/vm/pin_user_pages.rst for details. +* see Documentation/core-api/pin_user_pages.rst for details. * -* This is intended for Case 1 (DIO) in Documentation/vm/pin_user_pages.rst. It +* This is intended for Case 1 (DIO) in Documentation/core-api/pin_user_pages.rst. It * is NOT intended for Case 2 (RDMA: long-term pins). */ long pin_user_pages(unsigned long start, unsigned long nr_pages,virt/kvm/arm/vgic/vgic-mmio-v3.c +1
-1@@ -300,7 +300,7 @@ static unsigned long vgic_v3_uaccess_read_pending(struct kvm_vcpu *vcpu,* pending state of interrupt is latched in pending_latch variable. * Userspace will save and restore pending state and line_level * separately. -* Refer to Documentation/virt/kvm/devices/arm-vgic-v3.txt +* Refer to Documentation/virt/kvm/devices/arm-vgic-v3.rst * for handling of ISPENDR and ICPENDR. */ for (i =0 ; i < len *8 ; i++) {virt/kvm/arm/vgic/vgic.h +2
-2@@ -42,7 +42,7 @@ VGIC_AFFINITY_LEVEL(val, 3))/* -* As per Documentation/virt/kvm/devices/arm-vgic-v3.txt, +* As per Documentation/virt/kvm/devices/arm-vgic-v3.rst, * below macros are defined for CPUREG encoding. */ #define KVM_REG_ARM_VGIC_SYSREG_OP0_MASK 0x000000000000c000@@ -63,7 +63,7 @@ KVM_REG_ARM_VGIC_SYSREG_OP2_MASK)/* -* As per Documentation/virt/kvm/devices/arm-vgic-its.txt, +* As per Documentation/virt/kvm/devices/arm-vgic-its.rst, * below macros are defined for ITS table entry encoding. */ #define KVM_ITS_CTE_VALID_SHIFT 63Signature · 1 line
2.24.1
Re: [PATCH 05/12] docs: dt: fix references to ap806-system-controller.txt
In reply to Mauro Carvalho ChehabHi Mauro,
Mauro Carvalho Chehab <[email protected]> wrote on Tue, 17 Mar 2020 14:10:44 +0100:
Quoted 7 lines
ap806-system-controller.txt was renamed to ap80x-system-controller.txt.
Update its references accordingly.
Fixes 2537831bbc19 ("dt-bindings: ap80x: replace AP806 with AP80x")Signed-off-by Mauro Carvalho Chehab <[email protected]>---
Thanks,
Miquèl
Re: [PATCH 04/12] docs: dt: fix references to m_can.txt file
In reply to Mauro Carvalho ChehabQuoted 10 lines · Mauro Carvalho Chehab
This file was converted to json and renamed. Update its references accordingly.
Fixes 824674b59f72 ("dt-bindings: net: can: Convert M_CAN to json-schema")Signed-off-by Mauro Carvalho Chehab <[email protected]>--- Documentation/devicetree/bindings/net/can/tcan4x5x.txt | 2 +- MAINTAINERS | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
Applied, thanks.
Rob
Re: [PATCH 05/12] docs: dt: fix references to ap806-system-controller.txt
In reply to Mauro Carvalho ChehabQuoted 11 lines · Mauro Carvalho Chehab
ap806-system-controller.txt was renamed to ap80x-system-controller.txt.
Update its references accordingly.
Fixes 2537831bbc19 ("dt-bindings: ap80x: replace AP806 with AP80x")Signed-off-by Mauro Carvalho Chehab <[email protected]>--- Documentation/devicetree/bindings/gpio/gpio-mvebu.txt | 2 +- Documentation/devicetree/bindings/thermal/armada-thermal.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
Applied, thanks.
Rob
Re: [PATCH 06/12] docs: dt: fix a broken reference to input.yaml
In reply to Mauro Carvalho ChehabQuoted 9 lines · Mauro Carvalho Chehab
The old file was converted to yaml, but its reference was still pointing to the old one.
Fixes 7cef1079e3ad ("dt-bindings: input: Add common input binding in json-schema")Signed-off-by Mauro Carvalho Chehab <[email protected]>--- Documentation/devicetree/bindings/arm/freescale/fsl,scu.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Applied, thanks.
Rob
Re: [PATCH 07/12] docs: dt: fix broken reference to phy-cadence-torrent.yaml
In reply to Mauro Carvalho ChehabQuoted 10 lines · Mauro Carvalho Chehab
This file was removed, and another file was added instead of it, on two separate commits.
Splitting a single logical change (doc conversion) on two patches is a bad thing, as it makes harder to discover what crap happened.
Anyway, this patch fixes the broken reference, making it pointing to the new location of the file.
Quoted 7 lines
Fixes 922003733d42 ("dt-bindings: phy: Remove Cadence MHDP PHY dt binding")Fixes c6d8eef38b7f ("dt-bindings: phy: Add Cadence MHDP PHY bindings in YAML format.")Signed-off-by Mauro Carvalho Chehab <[email protected]>--- Documentation/devicetree/bindings/phy/ti,phy-j721e-wiz.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Re: [PATCH 10/12] docs: dt: display/ti: fix typos at the devicetree/ directory name
In reply to Mauro Carvalho ChehabQuoted 9 lines · Mauro Carvalho Chehab
The name of the devicetree directory is wrong on those three TI bindings:
Signed-off-by Mauro Carvalho Chehab <[email protected]>--- Documentation/devicetree/bindings/display/ti/ti,am65x-dss.yaml | 2 +- Documentation/devicetree/bindings/display/ti/ti,j721e-dss.yaml | 2 +- Documentation/devicetree/bindings/display/ti/ti,k2g-dss.yaml | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)
Applied to drm-misc.
Rob
Re: [PATCH 09/12] docs: fix broken references for ReST files that moved around
In reply to Mauro Carvalho ChehabQuoted 183 lines · Mauro Carvalho Chehab
Some broken references happened due to shifting files around and ReST renames. Those can't be auto-fixed by the script, so let's fix them manually.
Signed-off-by Mauro Carvalho Chehab <[email protected]>--- Documentation/doc-guide/maintainer-profile.rst | 2 +- Documentation/virt/kvm/mmu.rst | 2 +- Documentation/virt/kvm/review-checklist.rst | 2 +- arch/x86/kvm/mmu/mmu.c | 2 +- drivers/crypto/allwinner/sun8i-ce/sun8i-ce-cipher.c | 2 +- drivers/crypto/allwinner/sun8i-ce/sun8i-ce-core.c | 2 +- drivers/crypto/allwinner/sun8i-ss/sun8i-ss-cipher.c | 2 +- drivers/crypto/allwinner/sun8i-ss/sun8i-ss-core.c | 2 +- drivers/media/v4l2-core/v4l2-fwnode.c | 2 +- include/uapi/linux/kvm.h | 4 ++-- tools/include/uapi/linux/kvm.h | 4 ++-- 11 files changed, 13 insertions(+), 13 deletions(-)Documentation/doc-guide/maintainer-profile.rst +1
-1@@ -6,7 +6,7 @@ Documentation subsystem maintainer entry profile The documentation "subsystem" is the central coordinating point for the kernel's documentation and associated infrastructure. It covers the hierarchy under Documentation/ (with the exception of -Documentation/device-tree), various utilities under scripts/ and, at least +Documentation/devicetree), various utilities under scripts/ and, at least some of the time, LICENSES/. It's worth noting, though, that the boundaries of this subsystem are ratherDocumentation/virt/kvm/mmu.rst +1
-1@@ -319,7 +319,7 @@ Handling a page fault is performed as follows: - If both P bit and R/W bit of error code are set, this could possibly be handled as a "fast page fault" (fixed without taking the MMU lock). See - the description in Documentation/virt/kvm/locking.txt. + the description in Documentation/virt/kvm/locking.rst. - if needed, walk the guest page tables to determine the guest translation (gva->gpa or ngpa->gpa)Documentation/virt/kvm/review-checklist.rst +1
-1@@ -10,7 +10,7 @@ Review checklist for kvm patches 2. Patches should be against kvm.git master branch. 3. If the patch introduces or modifies a new userspace API: - - the API must be documented in Documentation/virt/kvm/api.txt + - the API must be documented in Documentation/virt/kvm/api.rst - the API must be discoverable using KVM_CHECK_EXTENSION 4. New state must include support for save/restore.arch/x86/kvm/mmu/mmu.c +1
-1@@ -3586,7 +3586,7 @@ static bool fast_page_fault(struct kvm_vcpu *vcpu, gpa_t cr2_or_gpa,/* * Currently, fast page fault only works for direct mapping * since the gfn is not stable for indirect shadow page. See -* Documentation/virt/kvm/locking.txt to get more detail. +* Documentation/virt/kvm/locking.rst to get more detail. */ fault_handled = fast_pf_fix_direct_spte(vcpu, sp, iterator.sptep, spte,drivers/crypto/allwinner/sun8i-ce/sun8i-ce-cipher.c +1
-1@@ -8,7 +8,7 @@* This file add support for AES cipher with 128,192,256 bits keysize in * CBC and ECB mode. * -* You could find a link for the datasheet in Documentation/arm/sunxi/README +* You could find a link for the datasheet in Documentation/arm/sunxi.rst */ #include <linux/crypto.h> drivers/crypto/allwinner/sun8i-ce/sun8i-ce-core.c +1
-1@@ -7,7 +7,7 @@* * Core file which registers crypto algorithms supported by the CryptoEngine. * -* You could find a link for the datasheet in Documentation/arm/sunxi/README +* You could find a link for the datasheet in Documentation/arm/sunxi.rst */ #include <linux/clk.h> #include <linux/crypto.h> drivers/crypto/allwinner/sun8i-ss/sun8i-ss-cipher.c +1
-1@@ -8,7 +8,7 @@* This file add support for AES cipher with 128,192,256 bits keysize in * CBC and ECB mode. * -* You could find a link for the datasheet in Documentation/arm/sunxi/README +* You could find a link for the datasheet in Documentation/arm/sunxi.rst */ #include <linux/crypto.h> drivers/crypto/allwinner/sun8i-ss/sun8i-ss-core.c +1
-1@@ -7,7 +7,7 @@* * Core file which registers crypto algorithms supported by the SecuritySystem * -* You could find a link for the datasheet in Documentation/arm/sunxi/README +* You could find a link for the datasheet in Documentation/arm/sunxi.rst */ #include <linux/clk.h> #include <linux/crypto.h> drivers/media/v4l2-core/v4l2-fwnode.c +1
-1@@ -980,7 +980,7 @@ static int v4l2_fwnode_reference_parse(struct device *dev,* * THIS EXAMPLE EXISTS MERELY TO DOCUMENT THIS FUNCTION. DO NOT USE IT AS A * REFERENCE IN HOW ACPI TABLES SHOULD BE WRITTEN!! See documentation under -* Documentation/acpi/dsd instead and especially graph.txt, +* Documentation/firmware-guide/acpi/dsd/ instead and especially graph.txt, * data-node-references.txt and leds.txt . * * Scope (\_SB.PCI0.I2C2) include/uapi/linux/kvm.h +2
-2@@ -116,7 +116,7 @@ struct kvm_irq_level {* ACPI gsi notion of irq. * For IA-64 (APIC model) IOAPIC0: irq 0-23; IOAPIC1: irq 24-47.. * For X86 (standard AT mode) PIC0/1: irq 0-15. IOAPIC0: 0-23.. -* For ARM: See Documentation/virt/kvm/api.txt +* For ARM: See Documentation/virt/kvm/api.rst */ union {__u32 irq;@@ -1106,7 +1106,7 @@ struct kvm_xen_hvm_config {* * KVM_IRQFD_FLAG_RESAMPLE indicates resamplefd is valid and specifies * the irqfd to operate in resampling mode for level triggered interrupt -* emulation. See Documentation/virt/kvm/api.txt. +* emulation. See Documentation/virt/kvm/api.rst. */ #define KVM_IRQFD_FLAG_RESAMPLE (1 << 1)tools/include/uapi/linux/kvm.h +2
-2@@ -116,7 +116,7 @@ struct kvm_irq_level {* ACPI gsi notion of irq. * For IA-64 (APIC model) IOAPIC0: irq 0-23; IOAPIC1: irq 24-47.. * For X86 (standard AT mode) PIC0/1: irq 0-15. IOAPIC0: 0-23.. -* For ARM: See Documentation/virt/kvm/api.txt +* For ARM: See Documentation/virt/kvm/api.rst */ union {__u32 irq;@@ -1100,7 +1100,7 @@ struct kvm_xen_hvm_config {* * KVM_IRQFD_FLAG_RESAMPLE indicates resamplefd is valid and specifies * the irqfd to operate in resampling mode for level triggered interrupt -* emulation. See Documentation/virt/kvm/api.txt. +* emulation. See Documentation/virt/kvm/api.rst. */ #define KVM_IRQFD_FLAG_RESAMPLE (1 << 1)Signature · 1 line
2.24.1
Hello
for sun8i-ss and sun8i-ce:
Thanks
_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Rob Herring
maintainerRe: [PATCH 02/12] MAINTAINERS: dt: update etnaviv file reference
In reply to Mauro Carvalho ChehabQuoted 9 lines · Mauro Carvalho Chehab
The etnaviv file was converted to json and renamed.
Update its reference accordingly.
Fixes 90aeca875f8a ("dt-bindings: display: Convert etnaviv to json-schema")Signed-off-by Mauro Carvalho Chehab <[email protected]>--- MAINTAINERS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Patches 2 and 3 applied.
Rob