[PATCH v2 00/20] Update Documentation/ cross-references

[PATCH v2 00/20] Update Documentation/ cross-references

[Mauro Carvalho Chehab]

Fix most broken documentation file cross references on next-20220624.

After this series, only 3 references will be broken:

Warning: Documentation/dev-tools/kunit/run_wrapper.rst references a file that doesn't exist: Documentation/dev-tools/kunit/non_uml.rst
Warning: Documentation/devicetree/bindings/regulator/siliconmitus,sm5703-regulator.yaml references a file that doesn't exist: Documentation/devicetree/bindings/mfd/siliconmitus,sm5703.yaml
Warning: drivers/acpi/device_pm.c references a file that doesn't exist: Documentation/firmware-guide/acpi/low-power-probe.rst

All of them seem to be due to the lack of a patch actually adding the
documentation. Maybe the document file is still under review?

Regards,
Mauro

Mauro Carvalho Chehab (20):
  docs: netdev: update maintainer-netdev.rst reference
  docs: filesystems: update netfs-api.rst reference
  docs: zh_CN: page_frags.rst: fix a broken reference
  docs: zh_CN/riscv/pmu.rst: remove old docuementation
  docs: zh_CN/devicetree: fix typos
  docs: zh_CN: fix a broken reference
  docs: zh_CN/vm: fix a typo for page reporting ReST file
  docs: zh_CN/vm/zsmalloc.rst: fix a typo
  docs: zh_CN/vm/index.rst: fix a broken reference
  Documentation: update watch_queue.rst references
  Documentation: KVM: update s390-pv.rst reference
  Documentation: KVM: update amd-memory-encryption.rst references
  Documentation: KVM: update msr.rst reference
  Documentation: KVM: update s390-diag.rst reference
  objtool: update objtool.txt references
  arch: m68k: q40: README: drop references to IDE driver
  tegra194-hte.rst: fix reference to its binding
  dt-bindings: mfd: update dlg,da9063.yaml reference
  MAINTAINERS: update nvidia,tegra20-host1x.yaml reference
  MAINTAINERS: fix cross references to mfd/dlg,da9063.yaml

 .../admin-guide/kernel-parameters.txt         |   2 +-
 .../bindings/input/da9062-onkey.txt           |   2 +-
 Documentation/driver-api/hte/tegra194-hte.rst |   2 +-
 Documentation/security/keys/core.rst          |   2 +-
 Documentation/security/secrets/coco.rst       |   2 +-
 .../it_IT/networking/netdev-FAQ.rst           |   2 +-
 .../translations/zh_CN/devicetree/index.rst   |   2 +-
 .../zh_CN/devicetree/of_unittest.rst          |   2 +-
 .../zh_CN/devicetree/usage-model.rst          |   2 +-
 .../zh_CN/doc-guide/kernel-doc.rst            |   2 +-
 .../translations/zh_CN/riscv/index.rst        |   1 -
 .../translations/zh_CN/riscv/pmu.rst          | 235 ------------------
 .../zh_CN/vm/free_page_reporting.rst          |   2 +-
 .../translations/zh_CN/vm/frontswap.rst       |   2 +-
 Documentation/translations/zh_CN/vm/index.rst |   2 +-
 .../translations/zh_CN/vm/page_frags.rst      |   2 +-
 .../translations/zh_CN/vm/zsmalloc.rst        |   2 +-
 Documentation/virt/kvm/api.rst                |   4 +-
 Documentation/virt/kvm/s390/s390-pv-boot.rst  |   2 +-
 Documentation/virt/kvm/x86/hypercalls.rst     |   2 +-
 Documentation/x86/orc-unwinder.rst            |   2 +-
 MAINTAINERS                                   |   6 +-
 arch/m68k/q40/README                          |   5 +-
 include/linux/fscache.h                       |   2 +-
 include/linux/objtool.h                       |   2 +-
 include/linux/watch_queue.h                   |   2 +-
 init/Kconfig                                  |   2 +-
 kernel/watch_queue.c                          |   2 +-
 lib/Kconfig.debug                             |   2 +-
 tools/include/linux/objtool.h                 |   2 +-
 tools/objtool/check.c                         |   2 +-
 31 files changed, 33 insertions(+), 270 deletions(-)
 delete mode 100644 Documentation/translations/zh_CN/riscv/pmu.rst

-- 
2.36.1

[PATCH v2 00/20] Update Documentation/ cross-references

[Mauro Carvalho Chehab]

Fix most broken documentation file cross references on next-20220624.

After this series, only 3 references will be broken:

Warning: Documentation/dev-tools/kunit/run_wrapper.rst references a file that doesn't exist: Documentation/dev-tools/kunit/non_uml.rst
Warning: Documentation/devicetree/bindings/regulator/siliconmitus,sm5703-regulator.yaml references a file that doesn't exist: Documentation/devicetree/bindings/mfd/siliconmitus,sm5703.yaml
Warning: drivers/acpi/device_pm.c references a file that doesn't exist: Documentation/firmware-guide/acpi/low-power-probe.rst

All of them seem to be due to the lack of a patch actually adding the
documentation. Maybe the document file is still under review?

Regards,
Mauro

Mauro Carvalho Chehab (20):
  docs: netdev: update maintainer-netdev.rst reference
  docs: filesystems: update netfs-api.rst reference
  docs: zh_CN: page_frags.rst: fix a broken reference
  docs: zh_CN/riscv/pmu.rst: remove old docuementation
  docs: zh_CN/devicetree: fix typos
  docs: zh_CN: fix a broken reference
  docs: zh_CN/vm: fix a typo for page reporting ReST file
  docs: zh_CN/vm/zsmalloc.rst: fix a typo
  docs: zh_CN/vm/index.rst: fix a broken reference
  Documentation: update watch_queue.rst references
  Documentation: KVM: update s390-pv.rst reference
  Documentation: KVM: update amd-memory-encryption.rst references
  Documentation: KVM: update msr.rst reference
  Documentation: KVM: update s390-diag.rst reference
  objtool: update objtool.txt references
  arch: m68k: q40: README: drop references to IDE driver
  tegra194-hte.rst: fix reference to its binding
  dt-bindings: mfd: update dlg,da9063.yaml reference
  MAINTAINERS: update nvidia,tegra20-host1x.yaml reference
  MAINTAINERS: fix cross references to mfd/dlg,da9063.yaml

 .../admin-guide/kernel-parameters.txt         |   2 +-
 .../bindings/input/da9062-onkey.txt           |   2 +-
 Documentation/driver-api/hte/tegra194-hte.rst |   2 +-
 Documentation/security/keys/core.rst          |   2 +-
 Documentation/security/secrets/coco.rst       |   2 +-
 .../it_IT/networking/netdev-FAQ.rst           |   2 +-
 .../translations/zh_CN/devicetree/index.rst   |   2 +-
 .../zh_CN/devicetree/of_unittest.rst          |   2 +-
 .../zh_CN/devicetree/usage-model.rst          |   2 +-
 .../zh_CN/doc-guide/kernel-doc.rst            |   2 +-
 .../translations/zh_CN/riscv/index.rst        |   1 -
 .../translations/zh_CN/riscv/pmu.rst          | 235 ------------------
 .../zh_CN/vm/free_page_reporting.rst          |   2 +-
 .../translations/zh_CN/vm/frontswap.rst       |   2 +-
 Documentation/translations/zh_CN/vm/index.rst |   2 +-
 .../translations/zh_CN/vm/page_frags.rst      |   2 +-
 .../translations/zh_CN/vm/zsmalloc.rst        |   2 +-
 Documentation/virt/kvm/api.rst                |   4 +-
 Documentation/virt/kvm/s390/s390-pv-boot.rst  |   2 +-
 Documentation/virt/kvm/x86/hypercalls.rst     |   2 +-
 Documentation/x86/orc-unwinder.rst            |   2 +-
 MAINTAINERS                                   |   6 +-
 arch/m68k/q40/README                          |   5 +-
 include/linux/fscache.h                       |   2 +-
 include/linux/objtool.h                       |   2 +-
 include/linux/watch_queue.h                   |   2 +-
 init/Kconfig                                  |   2 +-
 kernel/watch_queue.c                          |   2 +-
 lib/Kconfig.debug                             |   2 +-
 tools/include/linux/objtool.h                 |   2 +-
 tools/objtool/check.c                         |   2 +-
 31 files changed, 33 insertions(+), 270 deletions(-)
 delete mode 100644 Documentation/translations/zh_CN/riscv/pmu.rst

-- 
2.36.1



_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

[PATCH v2 01/20] docs: netdev: update maintainer-netdev.rst reference

[Mauro Carvalho Chehab]

Changeset 8df0136376dc ("docs: netdev: move the netdev-FAQ to the process pages")
renamed: Documentation/networking/netdev-FAQ.rst
to: Documentation/process/maintainer-netdev.rst.

Update its cross-reference accordingly.

Fixes: 8df0136376dc ("docs: netdev: move the netdev-FAQ to the process pages")
Acked-by: Jakub Kicinski <kuba@kernel.org>
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---

To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/

 Documentation/translations/it_IT/networking/netdev-FAQ.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/translations/it_IT/networking/netdev-FAQ.rst b/Documentation/translations/it_IT/networking/netdev-FAQ.rst
index 7e2456bb7d92..8a1e049585c0 100644
--- a/Documentation/translations/it_IT/networking/netdev-FAQ.rst
+++ b/Documentation/translations/it_IT/networking/netdev-FAQ.rst
@@ -1,6 +1,6 @@
 .. include:: ../disclaimer-ita.rst
 
-:Original: :ref:`Documentation/networking/netdev-FAQ.rst <netdev-FAQ>`
+:Original: :ref:`Documentation/process/maintainer-netdev.rst <netdev-FAQ>`
 
 .. _it_netdev-FAQ:
 
-- 
2.36.1

[PATCH v2 02/20] docs: filesystems: update netfs-api.rst reference

[Mauro Carvalho Chehab]

Changeset efc930fa1d84 ("docs: filesystems: caching/netfs-api.txt: convert it to ReST")
renamed: Documentation/filesystems/caching/netfs-api.txt
to: Documentation/filesystems/caching/netfs-api.rst.

Update its cross-reference accordingly.

Fixes: efc930fa1d84 ("docs: filesystems: caching/netfs-api.txt: convert it to ReST")
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---

To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/

 include/linux/fscache.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/linux/fscache.h b/include/linux/fscache.h
index 72585c9729a2..2f82ea31d4c1 100644
--- a/include/linux/fscache.h
+++ b/include/linux/fscache.h
@@ -378,7 +378,7 @@ void fscache_update_cookie(struct fscache_cookie *cookie, const void *aux_data,
  *
  * Request that the size of an object be changed.
  *
- * See Documentation/filesystems/caching/netfs-api.txt for a complete
+ * See Documentation/filesystems/caching/netfs-api.rst for a complete
  * description.
  */
 static inline
-- 
2.36.1

[PATCH v2 03/20] docs: zh_CN: page_frags.rst: fix a broken reference

[Mauro Carvalho Chehab]

typo:
	page_frag.rst -> page_frags.rst

Fixes: f51debc256f8 ("docs/zh_CN: add vm page_frags translation")
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---

To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/

 Documentation/translations/zh_CN/vm/page_frags.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/translations/zh_CN/vm/page_frags.rst b/Documentation/translations/zh_CN/vm/page_frags.rst
index ad27fed33634..38ecddb9e1c0 100644
--- a/Documentation/translations/zh_CN/vm/page_frags.rst
+++ b/Documentation/translations/zh_CN/vm/page_frags.rst
@@ -1,4 +1,4 @@
-:Original: Documentation/vm/page_frag.rst
+:Original: Documentation/vm/page_frags.rst
 
 :翻译:
 
-- 
2.36.1

Re: [PATCH v2 03/20] docs: zh_CN: page_frags.rst: fix a broken reference

[YanTeng Si]

在 2022/6/26 17:10, Mauro Carvalho Chehab 写道:
> typo:
> 	page_frag.rst -> page_frags.rst
>
> Fixes: f51debc256f8 ("docs/zh_CN: add vm page_frags translation")
> Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>

Acked-by: Yanteng Si<siyanteng@loongson.cn>

Thanks,
Yanteng

> ---
>
> To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
> See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/
>
>   Documentation/translations/zh_CN/vm/page_frags.rst | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/translations/zh_CN/vm/page_frags.rst b/Documentation/translations/zh_CN/vm/page_frags.rst
> index ad27fed33634..38ecddb9e1c0 100644
> --- a/Documentation/translations/zh_CN/vm/page_frags.rst
> +++ b/Documentation/translations/zh_CN/vm/page_frags.rst
> @@ -1,4 +1,4 @@
> -:Original: Documentation/vm/page_frag.rst
> +:Original: Documentation/vm/page_frags.rst
>   
>   :翻译:
>   

[PATCH v2 04/20] docs: zh_CN/riscv/pmu.rst: remove old docuementation

[Mauro Carvalho Chehab]

As the original doc was removed, it doesn't make sense to keep
its translation.

Fixes: 23b1f18326ec ("Documentation: riscv: Remove the old documentation")
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---

To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/

 .../translations/zh_CN/riscv/index.rst        |   1 -
 .../translations/zh_CN/riscv/pmu.rst          | 235 ------------------
 2 files changed, 236 deletions(-)
 delete mode 100644 Documentation/translations/zh_CN/riscv/pmu.rst

diff --git a/Documentation/translations/zh_CN/riscv/index.rst b/Documentation/translations/zh_CN/riscv/index.rst
index 614cde0c0997..131e405aa857 100644
--- a/Documentation/translations/zh_CN/riscv/index.rst
+++ b/Documentation/translations/zh_CN/riscv/index.rst
@@ -19,7 +19,6 @@ RISC-V 体系结构
 
     boot-image-header
     vm-layout
-    pmu
     patch-acceptance
 
 
diff --git a/Documentation/translations/zh_CN/riscv/pmu.rst b/Documentation/translations/zh_CN/riscv/pmu.rst
deleted file mode 100644
index 7ec801026c4d..000000000000
--- a/Documentation/translations/zh_CN/riscv/pmu.rst
+++ /dev/null
@@ -1,235 +0,0 @@
-.. include:: ../disclaimer-zh_CN.rst
-
-:Original: Documentation/riscv/pmu.rst
-
-:翻译:
-
- 司延腾 Yanteng Si <siyanteng@loongson.cn>
-
-.. _cn_riscv_pmu:
-
-========================
-RISC-V平台上对PMUs的支持
-========================
-
-Alan Kao <alankao@andestech.com>, Mar 2018
-
-简介
-------------
-
-截止本文撰写时，在The RISC-V ISA Privileged Version 1.10中提到的 perf_event
-相关特性如下:
-（详情请查阅手册）
-
-* [m|s]counteren
-* mcycle[h], cycle[h]
-* minstret[h], instret[h]
-* mhpeventx, mhpcounterx[h]
-
-仅有以上这些功能，移植perf需要做很多工作，究其原因是缺少以下通用架构的性能
-监测特性:
-
-* 启用/停用计数器
-  在我们这里，计数器一直在自由运行。
-* 计数器溢出引起的中断
-  规范中没有这种功能。
-* 中断指示器
-  不可能所有的计数器都有很多的中断端口，所以需要一个中断指示器让软件来判断
-  哪个计数器刚好溢出。
-* 写入计数器
-  由于内核不能修改计数器，所以会有一个SBI来支持这个功能[1]。 另外，一些厂商
-  考虑实现M-S-U型号机器的硬件扩展来直接写入计数器。
-
-这篇文档旨在为开发者提供一个在内核中支持PMU的简要指南。下面的章节简要解释了
-perf' 机制和待办事项。
-
-你可以在这里查看以前的讨论[1][2]。 另外，查看附录中的相关内核结构体可能会有
-帮助。
-
-
-1. 初始化
----------
-
-*riscv_pmu* 是一个类型为 *struct riscv_pmu* 的全局指针，它包含了根据perf内部
-约定的各种方法和PMU-specific参数。人们应该声明这样的实例来代表PMU。 默认情况
-下， *riscv_pmu* 指向一个常量结构体 *riscv_base_pmu* ，它对基准QEMU模型有非常
-基础的支持。
-
-
-然后他/她可以将实例的指针分配给 *riscv_pmu* ，这样就可以利用已经实现的最小逻
-辑，或者创建他/她自己的 *riscv_init_platform_pmu* 实现。
-
-换句话说，现有的 *riscv_base_pmu* 源只是提供了一个参考实现。 开发者可以灵活地
-决定多少部分可用，在最极端的情况下，他们可以根据自己的需要定制每一个函数。
-
-
-2. Event Initialization
------------------------
-
-当用户启动perf命令来监控一些事件时，首先会被用户空间的perf工具解释为多个
-*perf_event_open* 系统调用，然后进一步调用上一步分配的 *event_init* 成员函数
-的主体。 在 *riscv_base_pmu* 的情况下，就是 *riscv_event_init* 。
-
-该功能的主要目的是将用户提供的事件翻译成映射图，从而可以直接对HW-related的控
-制寄存器或计数器进行操作。该翻译基于 *riscv_pmu* 中提供的映射和方法。
-
-注意，有些功能也可以在这个阶段完成:
-
-(1) 中断设置，这个在下一节说；
-(2) 特限级设置(仅用户空间、仅内核空间、两者都有)；
-(3) 析构函数设置。 通常应用 *riscv_destroy_event* 即可；
-(4) 对非采样事件的调整，这将被函数应用，如 *perf_adjust_period* ，通常如下::
-
-      if (!is_sampling_event(event)) {
-              hwc->sample_period = x86_pmu.max_period;
-              hwc->last_period = hwc->sample_period;
-              local64_set(&hwc->period_left, hwc->sample_period);
-      }
-
-
-在 *riscv_base_pmu* 的情况下，目前只提供了（3）。
-
-
-3. 中断
--------
-
-3.1. 中断初始化
-
-这种情况经常出现在 *event_init* 方案的开头。通常情况下，这应该是一个代码段，如::
-
-  int x86_reserve_hardware(void)
-  {
-        int err = 0;
-
-        if (!atomic_inc_not_zero(&pmc_refcount)) {
-                mutex_lock(&pmc_reserve_mutex);
-                if (atomic_read(&pmc_refcount) == 0) {
-                        if (!reserve_pmc_hardware())
-                                err = -EBUSY;
-                        else
-                                reserve_ds_buffers();
-                }
-                if (!err)
-                        atomic_inc(&pmc_refcount);
-                mutex_unlock(&pmc_reserve_mutex);
-        }
-
-        return err;
-  }
-
-而神奇的是 *reserve_pmc_hardware* ，它通常做原子操作，使实现的IRQ可以从某个全局函
-数指针访问。 而 *release_pmc_hardware* 的作用正好相反，它用在上一节提到的事件分配
-器中。
-
- (注：从所有架构的实现来看，*reserve/release* 对总是IRQ设置，所以 *pmc_hardware*
- 似乎有些误导。 它并不处理事件和物理计数器之间的绑定，这一点将在下一节介绍。)
-
-3.2. IRQ结构体
-
-基本上，一个IRQ运行以下伪代码::
-
-  for each hardware counter that triggered this overflow
-
-      get the event of this counter
-
-      // following two steps are defined as *read()*,
-      // check the section Reading/Writing Counters for details.
-      count the delta value since previous interrupt
-      update the event->count (# event occurs) by adding delta, and
-                 event->hw.period_left by subtracting delta
-
-      if the event overflows
-          sample data
-          set the counter appropriately for the next overflow
-
-          if the event overflows again
-              too frequently, throttle this event
-          fi
-      fi
-
-  end for
-
- 然而截至目前，没有一个RISC-V的实现为perf设计了中断，所以具体的实现要在未来完成。
-
-4. Reading/Writing 计数
------------------------
-
-它们看似差不多，但perf对待它们的态度却截然不同。 对于读，在 *struct pmu* 中有一个
-*read* 接口，但它的作用不仅仅是读。 根据上下文，*read* 函数不仅要读取计数器的内容
-（event->count），还要更新左周期到下一个中断（event->hw.period_left）。
-
- 但 perf 的核心不需要直接写计数器。 写计数器隐藏在以下两点的抽象化之后，
- 1） *pmu->start* ，从字面上看就是开始计数，所以必须把计数器设置成一个合适的值，以
- 便下一次中断；
- 2）在IRQ里面，应该把计数器设置成同样的合理值。
-
-在RISC-V中，读操作不是问题，但写操作就需要费些力气了，因为S模式不允许写计数器。
-
-
-5. add()/del()/start()/stop()
------------------------------
-
-基本思想: add()/del() 向PMU添加/删除事件，start()/stop() 启动/停止PMU中某个事件
-的计数器。 所有这些函数都使用相同的参数: *struct perf_event *event* 和 *int flag* 。
-
-把 perf 看作一个状态机，那么你会发现这些函数作为这些状态之间的状态转换过程。
-定义了三种状态（event->hw.state）:
-
-* PERF_HES_STOPPED:	计数停止
-* PERF_HES_UPTODATE:	event->count是最新的
-* PERF_HES_ARCH:	依赖于体系结构的用法，。。。我们现在并不需要它。
-
-这些状态转换的正常流程如下:
-
-* 用户启动一个 perf 事件，导致调用 *event_init* 。
-* 当被上下文切换进来的时候，*add* 会被 perf core 调用，并带有一个标志 PERF_EF_START，
-  也就是说事件被添加后应该被启动。 在这个阶段，如果有的话，一般事件会被绑定到一个物
-  理计数器上。当状态变为PERF_HES_STOPPED和PERF_HES_UPTODATE，因为现在已经停止了,
-  （软件）事件计数不需要更新。
-
-  - 然后调用 *start* ，并启用计数器。
-    通过PERF_EF_RELOAD标志，它向计数器写入一个适当的值（详细情况请参考上一节）。
-    如果标志不包含PERF_EF_RELOAD，则不会写入任何内容。
-    现在状态被重置为none，因为它既没有停止也没有更新（计数已经开始）。
-
-*当被上下文切换出来时被调用。 然后，它检查出PMU中的所有事件，并调用 *stop* 来更新它们
- 的计数。
-
-  - *stop* 被 *del* 和perf核心调用，标志为PERF_EF_UPDATE，它经常以相同的逻辑和 *read*
-    共用同一个子程序。
-    状态又一次变为PERF_HES_STOPPED和PERF_HES_UPTODATE。
-
-  - 这两对程序的生命周期: *add* 和 *del* 在任务切换时被反复调用；*start* 和 *stop* 在
-    perf核心需要快速停止和启动时也会被调用，比如在调整中断周期时。
-
-目前的实现已经足够了，将来可以很容易地扩展到功能。
-
-A. 相关结构体
--------------
-
-* struct pmu: include/linux/perf_event.h
-* struct riscv_pmu: arch/riscv/include/asm/perf_event.h
-
-  两个结构体都被设计为只读。
-
-  *struct pmu* 定义了一些函数指针接口，它们大多以 *struct perf_event* 作为主参数，根据
-  perf的内部状态机处理perf事件（详情请查看kernel/events/core.c）。
-
-  *struct riscv_pmu* 定义了PMU的具体参数。 命名遵循所有其它架构的惯例。
-
-* struct perf_event: include/linux/perf_event.h
-* struct hw_perf_event
-
-  表示 perf 事件的通用结构体，以及硬件相关的细节。
-
-* struct riscv_hw_events: arch/riscv/include/asm/perf_event.h
-
-  保存事件状态的结构有两个固定成员。
-  事件的数量和事件的数组。
-
-参考文献
---------
-
-[1] https://github.com/riscv/riscv-linux/pull/124
-
-[2] https://groups.google.com/a/groups.riscv.org/forum/#!topic/sw-dev/f19TmCNP6yA
-- 
2.36.1

[PATCH v2 04/20] docs: zh_CN/riscv/pmu.rst: remove old docuementation

[Mauro Carvalho Chehab]

As the original doc was removed, it doesn't make sense to keep
its translation.

Fixes: 23b1f18326ec ("Documentation: riscv: Remove the old documentation")
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---

To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/

 .../translations/zh_CN/riscv/index.rst        |   1 -
 .../translations/zh_CN/riscv/pmu.rst          | 235 ------------------
 2 files changed, 236 deletions(-)
 delete mode 100644 Documentation/translations/zh_CN/riscv/pmu.rst

diff --git a/Documentation/translations/zh_CN/riscv/index.rst b/Documentation/translations/zh_CN/riscv/index.rst
index 614cde0c0997..131e405aa857 100644
--- a/Documentation/translations/zh_CN/riscv/index.rst
+++ b/Documentation/translations/zh_CN/riscv/index.rst
@@ -19,7 +19,6 @@ RISC-V 体系结构
 
     boot-image-header
     vm-layout
-    pmu
     patch-acceptance
 
 
diff --git a/Documentation/translations/zh_CN/riscv/pmu.rst b/Documentation/translations/zh_CN/riscv/pmu.rst
deleted file mode 100644
index 7ec801026c4d..000000000000
--- a/Documentation/translations/zh_CN/riscv/pmu.rst
+++ /dev/null
@@ -1,235 +0,0 @@
-.. include:: ../disclaimer-zh_CN.rst
-
-:Original: Documentation/riscv/pmu.rst
-
-:翻译:
-
- 司延腾 Yanteng Si <siyanteng@loongson.cn>
-
-.. _cn_riscv_pmu:
-
-========================
-RISC-V平台上对PMUs的支持
-========================
-
-Alan Kao <alankao@andestech.com>, Mar 2018
-
-简介
-------------
-
-截止本文撰写时，在The RISC-V ISA Privileged Version 1.10中提到的 perf_event
-相关特性如下:
-（详情请查阅手册）
-
-* [m|s]counteren
-* mcycle[h], cycle[h]
-* minstret[h], instret[h]
-* mhpeventx, mhpcounterx[h]
-
-仅有以上这些功能，移植perf需要做很多工作，究其原因是缺少以下通用架构的性能
-监测特性:
-
-* 启用/停用计数器
-  在我们这里，计数器一直在自由运行。
-* 计数器溢出引起的中断
-  规范中没有这种功能。
-* 中断指示器
-  不可能所有的计数器都有很多的中断端口，所以需要一个中断指示器让软件来判断
-  哪个计数器刚好溢出。
-* 写入计数器
-  由于内核不能修改计数器，所以会有一个SBI来支持这个功能[1]。 另外，一些厂商
-  考虑实现M-S-U型号机器的硬件扩展来直接写入计数器。
-
-这篇文档旨在为开发者提供一个在内核中支持PMU的简要指南。下面的章节简要解释了
-perf' 机制和待办事项。
-
-你可以在这里查看以前的讨论[1][2]。 另外，查看附录中的相关内核结构体可能会有
-帮助。
-
-
-1. 初始化
----------
-
-*riscv_pmu* 是一个类型为 *struct riscv_pmu* 的全局指针，它包含了根据perf内部
-约定的各种方法和PMU-specific参数。人们应该声明这样的实例来代表PMU。 默认情况
-下， *riscv_pmu* 指向一个常量结构体 *riscv_base_pmu* ，它对基准QEMU模型有非常
-基础的支持。
-
-
-然后他/她可以将实例的指针分配给 *riscv_pmu* ，这样就可以利用已经实现的最小逻
-辑，或者创建他/她自己的 *riscv_init_platform_pmu* 实现。
-
-换句话说，现有的 *riscv_base_pmu* 源只是提供了一个参考实现。 开发者可以灵活地
-决定多少部分可用，在最极端的情况下，他们可以根据自己的需要定制每一个函数。
-
-
-2. Event Initialization
------------------------
-
-当用户启动perf命令来监控一些事件时，首先会被用户空间的perf工具解释为多个
-*perf_event_open* 系统调用，然后进一步调用上一步分配的 *event_init* 成员函数
-的主体。 在 *riscv_base_pmu* 的情况下，就是 *riscv_event_init* 。
-
-该功能的主要目的是将用户提供的事件翻译成映射图，从而可以直接对HW-related的控
-制寄存器或计数器进行操作。该翻译基于 *riscv_pmu* 中提供的映射和方法。
-
-注意，有些功能也可以在这个阶段完成:
-
-(1) 中断设置，这个在下一节说；
-(2) 特限级设置(仅用户空间、仅内核空间、两者都有)；
-(3) 析构函数设置。 通常应用 *riscv_destroy_event* 即可；
-(4) 对非采样事件的调整，这将被函数应用，如 *perf_adjust_period* ，通常如下::
-
-      if (!is_sampling_event(event)) {
-              hwc->sample_period = x86_pmu.max_period;
-              hwc->last_period = hwc->sample_period;
-              local64_set(&hwc->period_left, hwc->sample_period);
-      }
-
-
-在 *riscv_base_pmu* 的情况下，目前只提供了（3）。
-
-
-3. 中断
--------
-
-3.1. 中断初始化
-
-这种情况经常出现在 *event_init* 方案的开头。通常情况下，这应该是一个代码段，如::
-
-  int x86_reserve_hardware(void)
-  {
-        int err = 0;
-
-        if (!atomic_inc_not_zero(&pmc_refcount)) {
-                mutex_lock(&pmc_reserve_mutex);
-                if (atomic_read(&pmc_refcount) == 0) {
-                        if (!reserve_pmc_hardware())
-                                err = -EBUSY;
-                        else
-                                reserve_ds_buffers();
-                }
-                if (!err)
-                        atomic_inc(&pmc_refcount);
-                mutex_unlock(&pmc_reserve_mutex);
-        }
-
-        return err;
-  }
-
-而神奇的是 *reserve_pmc_hardware* ，它通常做原子操作，使实现的IRQ可以从某个全局函
-数指针访问。 而 *release_pmc_hardware* 的作用正好相反，它用在上一节提到的事件分配
-器中。
-
- (注：从所有架构的实现来看，*reserve/release* 对总是IRQ设置，所以 *pmc_hardware*
- 似乎有些误导。 它并不处理事件和物理计数器之间的绑定，这一点将在下一节介绍。)
-
-3.2. IRQ结构体
-
-基本上，一个IRQ运行以下伪代码::
-
-  for each hardware counter that triggered this overflow
-
-      get the event of this counter
-
-      // following two steps are defined as *read()*,
-      // check the section Reading/Writing Counters for details.
-      count the delta value since previous interrupt
-      update the event->count (# event occurs) by adding delta, and
-                 event->hw.period_left by subtracting delta
-
-      if the event overflows
-          sample data
-          set the counter appropriately for the next overflow
-
-          if the event overflows again
-              too frequently, throttle this event
-          fi
-      fi
-
-  end for
-
- 然而截至目前，没有一个RISC-V的实现为perf设计了中断，所以具体的实现要在未来完成。
-
-4. Reading/Writing 计数
------------------------
-
-它们看似差不多，但perf对待它们的态度却截然不同。 对于读，在 *struct pmu* 中有一个
-*read* 接口，但它的作用不仅仅是读。 根据上下文，*read* 函数不仅要读取计数器的内容
-（event->count），还要更新左周期到下一个中断（event->hw.period_left）。
-
- 但 perf 的核心不需要直接写计数器。 写计数器隐藏在以下两点的抽象化之后，
- 1） *pmu->start* ，从字面上看就是开始计数，所以必须把计数器设置成一个合适的值，以
- 便下一次中断；
- 2）在IRQ里面，应该把计数器设置成同样的合理值。
-
-在RISC-V中，读操作不是问题，但写操作就需要费些力气了，因为S模式不允许写计数器。
-
-
-5. add()/del()/start()/stop()
------------------------------
-
-基本思想: add()/del() 向PMU添加/删除事件，start()/stop() 启动/停止PMU中某个事件
-的计数器。 所有这些函数都使用相同的参数: *struct perf_event *event* 和 *int flag* 。
-
-把 perf 看作一个状态机，那么你会发现这些函数作为这些状态之间的状态转换过程。
-定义了三种状态（event->hw.state）:
-
-* PERF_HES_STOPPED:	计数停止
-* PERF_HES_UPTODATE:	event->count是最新的
-* PERF_HES_ARCH:	依赖于体系结构的用法，。。。我们现在并不需要它。
-
-这些状态转换的正常流程如下:
-
-* 用户启动一个 perf 事件，导致调用 *event_init* 。
-* 当被上下文切换进来的时候，*add* 会被 perf core 调用，并带有一个标志 PERF_EF_START，
-  也就是说事件被添加后应该被启动。 在这个阶段，如果有的话，一般事件会被绑定到一个物
-  理计数器上。当状态变为PERF_HES_STOPPED和PERF_HES_UPTODATE，因为现在已经停止了,
-  （软件）事件计数不需要更新。
-
-  - 然后调用 *start* ，并启用计数器。
-    通过PERF_EF_RELOAD标志，它向计数器写入一个适当的值（详细情况请参考上一节）。
-    如果标志不包含PERF_EF_RELOAD，则不会写入任何内容。
-    现在状态被重置为none，因为它既没有停止也没有更新（计数已经开始）。
-
-*当被上下文切换出来时被调用。 然后，它检查出PMU中的所有事件，并调用 *stop* 来更新它们
- 的计数。
-
-  - *stop* 被 *del* 和perf核心调用，标志为PERF_EF_UPDATE，它经常以相同的逻辑和 *read*
-    共用同一个子程序。
-    状态又一次变为PERF_HES_STOPPED和PERF_HES_UPTODATE。
-
-  - 这两对程序的生命周期: *add* 和 *del* 在任务切换时被反复调用；*start* 和 *stop* 在
-    perf核心需要快速停止和启动时也会被调用，比如在调整中断周期时。
-
-目前的实现已经足够了，将来可以很容易地扩展到功能。
-
-A. 相关结构体
--------------
-
-* struct pmu: include/linux/perf_event.h
-* struct riscv_pmu: arch/riscv/include/asm/perf_event.h
-
-  两个结构体都被设计为只读。
-
-  *struct pmu* 定义了一些函数指针接口，它们大多以 *struct perf_event* 作为主参数，根据
-  perf的内部状态机处理perf事件（详情请查看kernel/events/core.c）。
-
-  *struct riscv_pmu* 定义了PMU的具体参数。 命名遵循所有其它架构的惯例。
-
-* struct perf_event: include/linux/perf_event.h
-* struct hw_perf_event
-
-  表示 perf 事件的通用结构体，以及硬件相关的细节。
-
-* struct riscv_hw_events: arch/riscv/include/asm/perf_event.h
-
-  保存事件状态的结构有两个固定成员。
-  事件的数量和事件的数组。
-
-参考文献
---------
-
-[1] https://github.com/riscv/riscv-linux/pull/124
-
-[2] https://groups.google.com/a/groups.riscv.org/forum/#!topic/sw-dev/f19TmCNP6yA
-- 
2.36.1


_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

Re: [PATCH v2 04/20] docs: zh_CN/riscv/pmu.rst: remove old docuementation

[YanTeng Si]

在 2022/6/26 17:10, Mauro Carvalho Chehab 写道:
> As the original doc was removed, it doesn't make sense to keep
> its translation.
>
> Fixes: 23b1f18326ec ("Documentation: riscv: Remove the old documentation")
> Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
> ---
>
> To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
> See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/
>
>   .../translations/zh_CN/riscv/index.rst        |   1 -
>   .../translations/zh_CN/riscv/pmu.rst          | 235 ------------------

Thanks, it has been fixed by Binbin Zhou.

<https://lore.kernel.org/r/6fe45d69210300a6c065262470bce963f8dc0ec3.1654685338.git.zhoubinbin@loongson.cn>


Thanks,

Yanteng

>   2 files changed, 236 deletions(-)
>   delete mode 100644 Documentation/translations/zh_CN/riscv/pmu.rst
>
> diff --git a/Documentation/translations/zh_CN/riscv/index.rst b/Documentation/translations/zh_CN/riscv/index.rst
> index 614cde0c0997..131e405aa857 100644
> --- a/Documentation/translations/zh_CN/riscv/index.rst
> +++ b/Documentation/translations/zh_CN/riscv/index.rst
> @@ -19,7 +19,6 @@ RISC-V 体系结构
>   
>       boot-image-header
>       vm-layout
> -    pmu
>       patch-acceptance
>   
>   
> diff --git a/Documentation/translations/zh_CN/riscv/pmu.rst b/Documentation/translations/zh_CN/riscv/pmu.rst
> deleted file mode 100644
> index 7ec801026c4d..000000000000
> --- a/Documentation/translations/zh_CN/riscv/pmu.rst
> +++ /dev/null
> @@ -1,235 +0,0 @@
> -.. include:: ../disclaimer-zh_CN.rst
> -
> -:Original: Documentation/riscv/pmu.rst
> -
> -:翻译:
> -
> - 司延腾 Yanteng Si <siyanteng@loongson.cn>
> -
> -.. _cn_riscv_pmu:
> -
> -========================
> -RISC-V平台上对PMUs的支持
> -========================
> -
> -Alan Kao <alankao@andestech.com>, Mar 2018
> -
> -简介
> -------------
> -
> -截止本文撰写时，在The RISC-V ISA Privileged Version 1.10中提到的 perf_event
> -相关特性如下:
> -（详情请查阅手册）
> -
> -* [m|s]counteren
> -* mcycle[h], cycle[h]
> -* minstret[h], instret[h]
> -* mhpeventx, mhpcounterx[h]
> -
> -仅有以上这些功能，移植perf需要做很多工作，究其原因是缺少以下通用架构的性能
> -监测特性:
> -
> -* 启用/停用计数器
> -  在我们这里，计数器一直在自由运行。
> -* 计数器溢出引起的中断
> -  规范中没有这种功能。
> -* 中断指示器
> -  不可能所有的计数器都有很多的中断端口，所以需要一个中断指示器让软件来判断
> -  哪个计数器刚好溢出。
> -* 写入计数器
> -  由于内核不能修改计数器，所以会有一个SBI来支持这个功能[1]。 另外，一些厂商
> -  考虑实现M-S-U型号机器的硬件扩展来直接写入计数器。
> -
> -这篇文档旨在为开发者提供一个在内核中支持PMU的简要指南。下面的章节简要解释了
> -perf' 机制和待办事项。
> -
> -你可以在这里查看以前的讨论[1][2]。 另外，查看附录中的相关内核结构体可能会有
> -帮助。
> -
> -
> -1. 初始化
> ----------
> -
> -*riscv_pmu* 是一个类型为 *struct riscv_pmu* 的全局指针，它包含了根据perf内部
> -约定的各种方法和PMU-specific参数。人们应该声明这样的实例来代表PMU。 默认情况
> -下， *riscv_pmu* 指向一个常量结构体 *riscv_base_pmu* ，它对基准QEMU模型有非常
> -基础的支持。
> -
> -
> -然后他/她可以将实例的指针分配给 *riscv_pmu* ，这样就可以利用已经实现的最小逻
> -辑，或者创建他/她自己的 *riscv_init_platform_pmu* 实现。
> -
> -换句话说，现有的 *riscv_base_pmu* 源只是提供了一个参考实现。 开发者可以灵活地
> -决定多少部分可用，在最极端的情况下，他们可以根据自己的需要定制每一个函数。
> -
> -
> -2. Event Initialization
> ------------------------
> -
> -当用户启动perf命令来监控一些事件时，首先会被用户空间的perf工具解释为多个
> -*perf_event_open* 系统调用，然后进一步调用上一步分配的 *event_init* 成员函数
> -的主体。 在 *riscv_base_pmu* 的情况下，就是 *riscv_event_init* 。
> -
> -该功能的主要目的是将用户提供的事件翻译成映射图，从而可以直接对HW-related的控
> -制寄存器或计数器进行操作。该翻译基于 *riscv_pmu* 中提供的映射和方法。
> -
> -注意，有些功能也可以在这个阶段完成:
> -
> -(1) 中断设置，这个在下一节说；
> -(2) 特限级设置(仅用户空间、仅内核空间、两者都有)；
> -(3) 析构函数设置。 通常应用 *riscv_destroy_event* 即可；
> -(4) 对非采样事件的调整，这将被函数应用，如 *perf_adjust_period* ，通常如下::
> -
> -      if (!is_sampling_event(event)) {
> -              hwc->sample_period = x86_pmu.max_period;
> -              hwc->last_period = hwc->sample_period;
> -              local64_set(&hwc->period_left, hwc->sample_period);
> -      }
> -
> -
> -在 *riscv_base_pmu* 的情况下，目前只提供了（3）。
> -
> -
> -3. 中断
> --------
> -
> -3.1. 中断初始化
> -
> -这种情况经常出现在 *event_init* 方案的开头。通常情况下，这应该是一个代码段，如::
> -
> -  int x86_reserve_hardware(void)
> -  {
> -        int err = 0;
> -
> -        if (!atomic_inc_not_zero(&pmc_refcount)) {
> -                mutex_lock(&pmc_reserve_mutex);
> -                if (atomic_read(&pmc_refcount) == 0) {
> -                        if (!reserve_pmc_hardware())
> -                                err = -EBUSY;
> -                        else
> -                                reserve_ds_buffers();
> -                }
> -                if (!err)
> -                        atomic_inc(&pmc_refcount);
> -                mutex_unlock(&pmc_reserve_mutex);
> -        }
> -
> -        return err;
> -  }
> -
> -而神奇的是 *reserve_pmc_hardware* ，它通常做原子操作，使实现的IRQ可以从某个全局函
> -数指针访问。 而 *release_pmc_hardware* 的作用正好相反，它用在上一节提到的事件分配
> -器中。
> -
> - (注：从所有架构的实现来看，*reserve/release* 对总是IRQ设置，所以 *pmc_hardware*
> - 似乎有些误导。 它并不处理事件和物理计数器之间的绑定，这一点将在下一节介绍。)
> -
> -3.2. IRQ结构体
> -
> -基本上，一个IRQ运行以下伪代码::
> -
> -  for each hardware counter that triggered this overflow
> -
> -      get the event of this counter
> -
> -      // following two steps are defined as *read()*,
> -      // check the section Reading/Writing Counters for details.
> -      count the delta value since previous interrupt
> -      update the event->count (# event occurs) by adding delta, and
> -                 event->hw.period_left by subtracting delta
> -
> -      if the event overflows
> -          sample data
> -          set the counter appropriately for the next overflow
> -
> -          if the event overflows again
> -              too frequently, throttle this event
> -          fi
> -      fi
> -
> -  end for
> -
> - 然而截至目前，没有一个RISC-V的实现为perf设计了中断，所以具体的实现要在未来完成。
> -
> -4. Reading/Writing 计数
> ------------------------
> -
> -它们看似差不多，但perf对待它们的态度却截然不同。 对于读，在 *struct pmu* 中有一个
> -*read* 接口，但它的作用不仅仅是读。 根据上下文，*read* 函数不仅要读取计数器的内容
> -（event->count），还要更新左周期到下一个中断（event->hw.period_left）。
> -
> - 但 perf 的核心不需要直接写计数器。 写计数器隐藏在以下两点的抽象化之后，
> - 1） *pmu->start* ，从字面上看就是开始计数，所以必须把计数器设置成一个合适的值，以
> - 便下一次中断；
> - 2）在IRQ里面，应该把计数器设置成同样的合理值。
> -
> -在RISC-V中，读操作不是问题，但写操作就需要费些力气了，因为S模式不允许写计数器。
> -
> -
> -5. add()/del()/start()/stop()
> ------------------------------
> -
> -基本思想: add()/del() 向PMU添加/删除事件，start()/stop() 启动/停止PMU中某个事件
> -的计数器。 所有这些函数都使用相同的参数: *struct perf_event *event* 和 *int flag* 。
> -
> -把 perf 看作一个状态机，那么你会发现这些函数作为这些状态之间的状态转换过程。
> -定义了三种状态（event->hw.state）:
> -
> -* PERF_HES_STOPPED:	计数停止
> -* PERF_HES_UPTODATE:	event->count是最新的
> -* PERF_HES_ARCH:	依赖于体系结构的用法，。。。我们现在并不需要它。
> -
> -这些状态转换的正常流程如下:
> -
> -* 用户启动一个 perf 事件，导致调用 *event_init* 。
> -* 当被上下文切换进来的时候，*add* 会被 perf core 调用，并带有一个标志 PERF_EF_START，
> -  也就是说事件被添加后应该被启动。 在这个阶段，如果有的话，一般事件会被绑定到一个物
> -  理计数器上。当状态变为PERF_HES_STOPPED和PERF_HES_UPTODATE，因为现在已经停止了,
> -  （软件）事件计数不需要更新。
> -
> -  - 然后调用 *start* ，并启用计数器。
> -    通过PERF_EF_RELOAD标志，它向计数器写入一个适当的值（详细情况请参考上一节）。
> -    如果标志不包含PERF_EF_RELOAD，则不会写入任何内容。
> -    现在状态被重置为none，因为它既没有停止也没有更新（计数已经开始）。
> -
> -*当被上下文切换出来时被调用。 然后，它检查出PMU中的所有事件，并调用 *stop* 来更新它们
> - 的计数。
> -
> -  - *stop* 被 *del* 和perf核心调用，标志为PERF_EF_UPDATE，它经常以相同的逻辑和 *read*
> -    共用同一个子程序。
> -    状态又一次变为PERF_HES_STOPPED和PERF_HES_UPTODATE。
> -
> -  - 这两对程序的生命周期: *add* 和 *del* 在任务切换时被反复调用；*start* 和 *stop* 在
> -    perf核心需要快速停止和启动时也会被调用，比如在调整中断周期时。
> -
> -目前的实现已经足够了，将来可以很容易地扩展到功能。
> -
> -A. 相关结构体
> --------------
> -
> -* struct pmu: include/linux/perf_event.h
> -* struct riscv_pmu: arch/riscv/include/asm/perf_event.h
> -
> -  两个结构体都被设计为只读。
> -
> -  *struct pmu* 定义了一些函数指针接口，它们大多以 *struct perf_event* 作为主参数，根据
> -  perf的内部状态机处理perf事件（详情请查看kernel/events/core.c）。
> -
> -  *struct riscv_pmu* 定义了PMU的具体参数。 命名遵循所有其它架构的惯例。
> -
> -* struct perf_event: include/linux/perf_event.h
> -* struct hw_perf_event
> -
> -  表示 perf 事件的通用结构体，以及硬件相关的细节。
> -
> -* struct riscv_hw_events: arch/riscv/include/asm/perf_event.h
> -
> -  保存事件状态的结构有两个固定成员。
> -  事件的数量和事件的数组。
> -
> -参考文献
> ---------
> -
> -[1] https://github.com/riscv/riscv-linux/pull/124
> -
> -[2] https://groups.google.com/a/groups.riscv.org/forum/#!topic/sw-dev/f19TmCNP6yA


_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

Re: [PATCH v2 04/20] docs: zh_CN/riscv/pmu.rst: remove old docuementation

[YanTeng Si]

在 2022/6/26 17:10, Mauro Carvalho Chehab 写道:
> As the original doc was removed, it doesn't make sense to keep
> its translation.
>
> Fixes: 23b1f18326ec ("Documentation: riscv: Remove the old documentation")
> Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
> ---
>
> To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
> See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/
>
>   .../translations/zh_CN/riscv/index.rst        |   1 -
>   .../translations/zh_CN/riscv/pmu.rst          | 235 ------------------

Thanks, it has been fixed by Binbin Zhou.

<https://lore.kernel.org/r/6fe45d69210300a6c065262470bce963f8dc0ec3.1654685338.git.zhoubinbin@loongson.cn>


Thanks,

Yanteng

>   2 files changed, 236 deletions(-)
>   delete mode 100644 Documentation/translations/zh_CN/riscv/pmu.rst
>
> diff --git a/Documentation/translations/zh_CN/riscv/index.rst b/Documentation/translations/zh_CN/riscv/index.rst
> index 614cde0c0997..131e405aa857 100644
> --- a/Documentation/translations/zh_CN/riscv/index.rst
> +++ b/Documentation/translations/zh_CN/riscv/index.rst
> @@ -19,7 +19,6 @@ RISC-V 体系结构
>   
>       boot-image-header
>       vm-layout
> -    pmu
>       patch-acceptance
>   
>   
> diff --git a/Documentation/translations/zh_CN/riscv/pmu.rst b/Documentation/translations/zh_CN/riscv/pmu.rst
> deleted file mode 100644
> index 7ec801026c4d..000000000000
> --- a/Documentation/translations/zh_CN/riscv/pmu.rst
> +++ /dev/null
> @@ -1,235 +0,0 @@
> -.. include:: ../disclaimer-zh_CN.rst
> -
> -:Original: Documentation/riscv/pmu.rst
> -
> -:翻译:
> -
> - 司延腾 Yanteng Si <siyanteng@loongson.cn>
> -
> -.. _cn_riscv_pmu:
> -
> -========================
> -RISC-V平台上对PMUs的支持
> -========================
> -
> -Alan Kao <alankao@andestech.com>, Mar 2018
> -
> -简介
> -------------
> -
> -截止本文撰写时，在The RISC-V ISA Privileged Version 1.10中提到的 perf_event
> -相关特性如下:
> -（详情请查阅手册）
> -
> -* [m|s]counteren
> -* mcycle[h], cycle[h]
> -* minstret[h], instret[h]
> -* mhpeventx, mhpcounterx[h]
> -
> -仅有以上这些功能，移植perf需要做很多工作，究其原因是缺少以下通用架构的性能
> -监测特性:
> -
> -* 启用/停用计数器
> -  在我们这里，计数器一直在自由运行。
> -* 计数器溢出引起的中断
> -  规范中没有这种功能。
> -* 中断指示器
> -  不可能所有的计数器都有很多的中断端口，所以需要一个中断指示器让软件来判断
> -  哪个计数器刚好溢出。
> -* 写入计数器
> -  由于内核不能修改计数器，所以会有一个SBI来支持这个功能[1]。 另外，一些厂商
> -  考虑实现M-S-U型号机器的硬件扩展来直接写入计数器。
> -
> -这篇文档旨在为开发者提供一个在内核中支持PMU的简要指南。下面的章节简要解释了
> -perf' 机制和待办事项。
> -
> -你可以在这里查看以前的讨论[1][2]。 另外，查看附录中的相关内核结构体可能会有
> -帮助。
> -
> -
> -1. 初始化
> ----------
> -
> -*riscv_pmu* 是一个类型为 *struct riscv_pmu* 的全局指针，它包含了根据perf内部
> -约定的各种方法和PMU-specific参数。人们应该声明这样的实例来代表PMU。 默认情况
> -下， *riscv_pmu* 指向一个常量结构体 *riscv_base_pmu* ，它对基准QEMU模型有非常
> -基础的支持。
> -
> -
> -然后他/她可以将实例的指针分配给 *riscv_pmu* ，这样就可以利用已经实现的最小逻
> -辑，或者创建他/她自己的 *riscv_init_platform_pmu* 实现。
> -
> -换句话说，现有的 *riscv_base_pmu* 源只是提供了一个参考实现。 开发者可以灵活地
> -决定多少部分可用，在最极端的情况下，他们可以根据自己的需要定制每一个函数。
> -
> -
> -2. Event Initialization
> ------------------------
> -
> -当用户启动perf命令来监控一些事件时，首先会被用户空间的perf工具解释为多个
> -*perf_event_open* 系统调用，然后进一步调用上一步分配的 *event_init* 成员函数
> -的主体。 在 *riscv_base_pmu* 的情况下，就是 *riscv_event_init* 。
> -
> -该功能的主要目的是将用户提供的事件翻译成映射图，从而可以直接对HW-related的控
> -制寄存器或计数器进行操作。该翻译基于 *riscv_pmu* 中提供的映射和方法。
> -
> -注意，有些功能也可以在这个阶段完成:
> -
> -(1) 中断设置，这个在下一节说；
> -(2) 特限级设置(仅用户空间、仅内核空间、两者都有)；
> -(3) 析构函数设置。 通常应用 *riscv_destroy_event* 即可；
> -(4) 对非采样事件的调整，这将被函数应用，如 *perf_adjust_period* ，通常如下::
> -
> -      if (!is_sampling_event(event)) {
> -              hwc->sample_period = x86_pmu.max_period;
> -              hwc->last_period = hwc->sample_period;
> -              local64_set(&hwc->period_left, hwc->sample_period);
> -      }
> -
> -
> -在 *riscv_base_pmu* 的情况下，目前只提供了（3）。
> -
> -
> -3. 中断
> --------
> -
> -3.1. 中断初始化
> -
> -这种情况经常出现在 *event_init* 方案的开头。通常情况下，这应该是一个代码段，如::
> -
> -  int x86_reserve_hardware(void)
> -  {
> -        int err = 0;
> -
> -        if (!atomic_inc_not_zero(&pmc_refcount)) {
> -                mutex_lock(&pmc_reserve_mutex);
> -                if (atomic_read(&pmc_refcount) == 0) {
> -                        if (!reserve_pmc_hardware())
> -                                err = -EBUSY;
> -                        else
> -                                reserve_ds_buffers();
> -                }
> -                if (!err)
> -                        atomic_inc(&pmc_refcount);
> -                mutex_unlock(&pmc_reserve_mutex);
> -        }
> -
> -        return err;
> -  }
> -
> -而神奇的是 *reserve_pmc_hardware* ，它通常做原子操作，使实现的IRQ可以从某个全局函
> -数指针访问。 而 *release_pmc_hardware* 的作用正好相反，它用在上一节提到的事件分配
> -器中。
> -
> - (注：从所有架构的实现来看，*reserve/release* 对总是IRQ设置，所以 *pmc_hardware*
> - 似乎有些误导。 它并不处理事件和物理计数器之间的绑定，这一点将在下一节介绍。)
> -
> -3.2. IRQ结构体
> -
> -基本上，一个IRQ运行以下伪代码::
> -
> -  for each hardware counter that triggered this overflow
> -
> -      get the event of this counter
> -
> -      // following two steps are defined as *read()*,
> -      // check the section Reading/Writing Counters for details.
> -      count the delta value since previous interrupt
> -      update the event->count (# event occurs) by adding delta, and
> -                 event->hw.period_left by subtracting delta
> -
> -      if the event overflows
> -          sample data
> -          set the counter appropriately for the next overflow
> -
> -          if the event overflows again
> -              too frequently, throttle this event
> -          fi
> -      fi
> -
> -  end for
> -
> - 然而截至目前，没有一个RISC-V的实现为perf设计了中断，所以具体的实现要在未来完成。
> -
> -4. Reading/Writing 计数
> ------------------------
> -
> -它们看似差不多，但perf对待它们的态度却截然不同。 对于读，在 *struct pmu* 中有一个
> -*read* 接口，但它的作用不仅仅是读。 根据上下文，*read* 函数不仅要读取计数器的内容
> -（event->count），还要更新左周期到下一个中断（event->hw.period_left）。
> -
> - 但 perf 的核心不需要直接写计数器。 写计数器隐藏在以下两点的抽象化之后，
> - 1） *pmu->start* ，从字面上看就是开始计数，所以必须把计数器设置成一个合适的值，以
> - 便下一次中断；
> - 2）在IRQ里面，应该把计数器设置成同样的合理值。
> -
> -在RISC-V中，读操作不是问题，但写操作就需要费些力气了，因为S模式不允许写计数器。
> -
> -
> -5. add()/del()/start()/stop()
> ------------------------------
> -
> -基本思想: add()/del() 向PMU添加/删除事件，start()/stop() 启动/停止PMU中某个事件
> -的计数器。 所有这些函数都使用相同的参数: *struct perf_event *event* 和 *int flag* 。
> -
> -把 perf 看作一个状态机，那么你会发现这些函数作为这些状态之间的状态转换过程。
> -定义了三种状态（event->hw.state）:
> -
> -* PERF_HES_STOPPED:	计数停止
> -* PERF_HES_UPTODATE:	event->count是最新的
> -* PERF_HES_ARCH:	依赖于体系结构的用法，。。。我们现在并不需要它。
> -
> -这些状态转换的正常流程如下:
> -
> -* 用户启动一个 perf 事件，导致调用 *event_init* 。
> -* 当被上下文切换进来的时候，*add* 会被 perf core 调用，并带有一个标志 PERF_EF_START，
> -  也就是说事件被添加后应该被启动。 在这个阶段，如果有的话，一般事件会被绑定到一个物
> -  理计数器上。当状态变为PERF_HES_STOPPED和PERF_HES_UPTODATE，因为现在已经停止了,
> -  （软件）事件计数不需要更新。
> -
> -  - 然后调用 *start* ，并启用计数器。
> -    通过PERF_EF_RELOAD标志，它向计数器写入一个适当的值（详细情况请参考上一节）。
> -    如果标志不包含PERF_EF_RELOAD，则不会写入任何内容。
> -    现在状态被重置为none，因为它既没有停止也没有更新（计数已经开始）。
> -
> -*当被上下文切换出来时被调用。 然后，它检查出PMU中的所有事件，并调用 *stop* 来更新它们
> - 的计数。
> -
> -  - *stop* 被 *del* 和perf核心调用，标志为PERF_EF_UPDATE，它经常以相同的逻辑和 *read*
> -    共用同一个子程序。
> -    状态又一次变为PERF_HES_STOPPED和PERF_HES_UPTODATE。
> -
> -  - 这两对程序的生命周期: *add* 和 *del* 在任务切换时被反复调用；*start* 和 *stop* 在
> -    perf核心需要快速停止和启动时也会被调用，比如在调整中断周期时。
> -
> -目前的实现已经足够了，将来可以很容易地扩展到功能。
> -
> -A. 相关结构体
> --------------
> -
> -* struct pmu: include/linux/perf_event.h
> -* struct riscv_pmu: arch/riscv/include/asm/perf_event.h
> -
> -  两个结构体都被设计为只读。
> -
> -  *struct pmu* 定义了一些函数指针接口，它们大多以 *struct perf_event* 作为主参数，根据
> -  perf的内部状态机处理perf事件（详情请查看kernel/events/core.c）。
> -
> -  *struct riscv_pmu* 定义了PMU的具体参数。 命名遵循所有其它架构的惯例。
> -
> -* struct perf_event: include/linux/perf_event.h
> -* struct hw_perf_event
> -
> -  表示 perf 事件的通用结构体，以及硬件相关的细节。
> -
> -* struct riscv_hw_events: arch/riscv/include/asm/perf_event.h
> -
> -  保存事件状态的结构有两个固定成员。
> -  事件的数量和事件的数组。
> -
> -参考文献
> ---------
> -
> -[1] https://github.com/riscv/riscv-linux/pull/124
> -
> -[2] https://groups.google.com/a/groups.riscv.org/forum/#!topic/sw-dev/f19TmCNP6yA

[PATCH v2 05/20] docs: zh_CN/devicetree: fix typos

[Mauro Carvalho Chehab]

The devicetree directory was using wrong case:

	Devicetree/ -> devicetree/

Fixes: a17b0169f29b ("docs/zh_CN: add devicetree index translation")
Fixes: c56481299df3 ("docs/zh_CN: add devicetree usage-model translation")
Fixes: 09d4466d3f3c ("docs/zh_CN: add devicetree of_unittest translation")
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---

To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/

 Documentation/translations/zh_CN/devicetree/index.rst       | 2 +-
 Documentation/translations/zh_CN/devicetree/of_unittest.rst | 2 +-
 Documentation/translations/zh_CN/devicetree/usage-model.rst | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/Documentation/translations/zh_CN/devicetree/index.rst b/Documentation/translations/zh_CN/devicetree/index.rst
index 23d0b6fccd58..3fc355fe0037 100644
--- a/Documentation/translations/zh_CN/devicetree/index.rst
+++ b/Documentation/translations/zh_CN/devicetree/index.rst
@@ -1,7 +1,7 @@
 .. SPDX-License-Identifier: GPL-2.0
 .. include:: ../disclaimer-zh_CN.rst
 
-:Original: Documentation/Devicetree/index.rst
+:Original: Documentation/devicetree/index.rst
 
 :翻译:
 
diff --git a/Documentation/translations/zh_CN/devicetree/of_unittest.rst b/Documentation/translations/zh_CN/devicetree/of_unittest.rst
index abd94e771ef8..11eb08ca8866 100644
--- a/Documentation/translations/zh_CN/devicetree/of_unittest.rst
+++ b/Documentation/translations/zh_CN/devicetree/of_unittest.rst
@@ -1,7 +1,7 @@
 .. SPDX-License-Identifier: GPL-2.0
 .. include:: ../disclaimer-zh_CN.rst
 
-:Original: Documentation/Devicetree/of_unittest.rst
+:Original: Documentation/devicetree/of_unittest.rst
 
 :翻译:
 
diff --git a/Documentation/translations/zh_CN/devicetree/usage-model.rst b/Documentation/translations/zh_CN/devicetree/usage-model.rst
index accdc33475a0..c6aee82c7e6e 100644
--- a/Documentation/translations/zh_CN/devicetree/usage-model.rst
+++ b/Documentation/translations/zh_CN/devicetree/usage-model.rst
@@ -1,7 +1,7 @@
 .. SPDX-License-Identifier: GPL-2.0
 .. include:: ../disclaimer-zh_CN.rst
 
-:Original: Documentation/Devicetree/usage-model.rst
+:Original: Documentation/devicetree/usage-model.rst
 
 :翻译:
 
-- 
2.36.1

Re: [PATCH v2 05/20] docs: zh_CN/devicetree: fix typos

[YanTeng Si]

在 2022/6/26 17:10, Mauro Carvalho Chehab 写道:
> The devicetree directory was using wrong case:
>
> 	Devicetree/ -> devicetree/
>
> Fixes: a17b0169f29b ("docs/zh_CN: add devicetree index translation")
> Fixes: c56481299df3 ("docs/zh_CN: add devicetree usage-model translation")
> Fixes: 09d4466d3f3c ("docs/zh_CN: add devicetree of_unittest translation")
> Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>

Acked-by: Yanteng Si<siyanteng@loongson.cn>

Thanks,
Yanteng

> ---
>
> To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
> See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/
>
>   Documentation/translations/zh_CN/devicetree/index.rst       | 2 +-
>   Documentation/translations/zh_CN/devicetree/of_unittest.rst | 2 +-
>   Documentation/translations/zh_CN/devicetree/usage-model.rst | 2 +-
>   3 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/translations/zh_CN/devicetree/index.rst b/Documentation/translations/zh_CN/devicetree/index.rst
> index 23d0b6fccd58..3fc355fe0037 100644
> --- a/Documentation/translations/zh_CN/devicetree/index.rst
> +++ b/Documentation/translations/zh_CN/devicetree/index.rst
> @@ -1,7 +1,7 @@
>   .. SPDX-License-Identifier: GPL-2.0
>   .. include:: ../disclaimer-zh_CN.rst
>   
> -:Original: Documentation/Devicetree/index.rst
> +:Original: Documentation/devicetree/index.rst
>   
>   :翻译:
>   
> diff --git a/Documentation/translations/zh_CN/devicetree/of_unittest.rst b/Documentation/translations/zh_CN/devicetree/of_unittest.rst
> index abd94e771ef8..11eb08ca8866 100644
> --- a/Documentation/translations/zh_CN/devicetree/of_unittest.rst
> +++ b/Documentation/translations/zh_CN/devicetree/of_unittest.rst
> @@ -1,7 +1,7 @@
>   .. SPDX-License-Identifier: GPL-2.0
>   .. include:: ../disclaimer-zh_CN.rst
>   
> -:Original: Documentation/Devicetree/of_unittest.rst
> +:Original: Documentation/devicetree/of_unittest.rst
>   
>   :翻译:
>   
> diff --git a/Documentation/translations/zh_CN/devicetree/usage-model.rst b/Documentation/translations/zh_CN/devicetree/usage-model.rst
> index accdc33475a0..c6aee82c7e6e 100644
> --- a/Documentation/translations/zh_CN/devicetree/usage-model.rst
> +++ b/Documentation/translations/zh_CN/devicetree/usage-model.rst
> @@ -1,7 +1,7 @@
>   .. SPDX-License-Identifier: GPL-2.0
>   .. include:: ../disclaimer-zh_CN.rst
>   
> -:Original: Documentation/Devicetree/usage-model.rst
> +:Original: Documentation/devicetree/usage-model.rst
>   
>   :翻译:
>   

[PATCH v2 06/20] docs: zh_CN: fix a broken reference

[Mauro Carvalho Chehab]

The location of the rust doc is wrong (probably a typo). Fix it.

Fixes: 3a5915156429 ("docs/zh_CN: Add translation zh_CN/doc-guide/kernel-doc.rst")
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---

To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/

 Documentation/translations/zh_CN/doc-guide/kernel-doc.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/translations/zh_CN/doc-guide/kernel-doc.rst b/Documentation/translations/zh_CN/doc-guide/kernel-doc.rst
index 82ec84470c0b..ccfb9b8329c2 100644
--- a/Documentation/translations/zh_CN/doc-guide/kernel-doc.rst
+++ b/Documentation/translations/zh_CN/doc-guide/kernel-doc.rst
@@ -14,7 +14,7 @@ Linux内核源文件可以包含kernel-doc格式的结构化文档注释，用
           实际有着明显的不同。内核源包含成千上万个kernel-doc注释。请坚持遵循
           此处描述的风格。
 
-.. note:: kernel-doc无法包含Rust代码：请参考 Documentation/rust/docs.rst 。
+.. note:: kernel-doc无法包含Rust代码：请参考 Documentation/rust/general-information.rst 。
 
 从注释中提取kernel-doc结构，并从中生成适当的 `Sphinx C 域`_ 函数和带有锚点的
 类型描述。这些注释将被过滤以生成特殊kernel-doc高亮和交叉引用。详见下文。
-- 
2.36.1

Re: [PATCH v2 06/20] docs: zh_CN: fix a broken reference

[Miguel Ojeda]

On Sun, Jun 26, 2022 at 11:11 AM Mauro Carvalho Chehab
<mchehab@kernel.org> wrote:
>
> The location of the rust doc is wrong (probably a typo). Fix it.

Thanks Mauro -- it was the old location of the document. For some
reason, the translated docs have bits from -next.

Cheers,
Miguel

[PATCH v2 07/20] docs: zh_CN/vm: fix a typo for page reporting ReST file

[Mauro Carvalho Chehab]

typo:
	_free_page_reporting.rst -> free_page_reporting.rst

Fixes: 9859b277bffe ("docs/zh_CN: add vm frontswap translation")
Fixes: adeacecbd36c ("docs/zh_CN: add free_page_reporting translation")
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---

To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/

 Documentation/translations/zh_CN/vm/free_page_reporting.rst | 2 +-
 Documentation/translations/zh_CN/vm/frontswap.rst           | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/translations/zh_CN/vm/free_page_reporting.rst b/Documentation/translations/zh_CN/vm/free_page_reporting.rst
index 31d6c34b956b..14336a3aa5f4 100644
--- a/Documentation/translations/zh_CN/vm/free_page_reporting.rst
+++ b/Documentation/translations/zh_CN/vm/free_page_reporting.rst
@@ -1,6 +1,6 @@
 .. include:: ../disclaimer-zh_CN.rst
 
-:Original: Documentation/vm/_free_page_reporting.rst
+:Original: Documentation/vm/free_page_reporting.rst
 
 :翻译:
 
diff --git a/Documentation/translations/zh_CN/vm/frontswap.rst b/Documentation/translations/zh_CN/vm/frontswap.rst
index 3eb07870e2ef..98aa6f581ea7 100644
--- a/Documentation/translations/zh_CN/vm/frontswap.rst
+++ b/Documentation/translations/zh_CN/vm/frontswap.rst
@@ -1,4 +1,4 @@
-:Original: Documentation/vm/_free_page_reporting.rst
+:Original: Documentation/vm/free_page_reporting.rst
 
 :翻译:
 
-- 
2.36.1

Re: [PATCH v2 07/20] docs: zh_CN/vm: fix a typo for page reporting ReST file

[YanTeng Si]

在 2022/6/26 17:10, Mauro Carvalho Chehab 写道:
> typo:
> 	_free_page_reporting.rst -> free_page_reporting.rst
>
> Fixes: 9859b277bffe ("docs/zh_CN: add vm frontswap translation")
> Fixes: adeacecbd36c ("docs/zh_CN: add free_page_reporting translation")
> Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>

Acked-by: Yanteng Si<siyanteng@loongson.cn>

Thanks,
Yanteng

> ---
>
> To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
> See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/
>
>   Documentation/translations/zh_CN/vm/free_page_reporting.rst | 2 +-
>   Documentation/translations/zh_CN/vm/frontswap.rst           | 2 +-
>   2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/translations/zh_CN/vm/free_page_reporting.rst b/Documentation/translations/zh_CN/vm/free_page_reporting.rst
> index 31d6c34b956b..14336a3aa5f4 100644
> --- a/Documentation/translations/zh_CN/vm/free_page_reporting.rst
> +++ b/Documentation/translations/zh_CN/vm/free_page_reporting.rst
> @@ -1,6 +1,6 @@
>   .. include:: ../disclaimer-zh_CN.rst
>   
> -:Original: Documentation/vm/_free_page_reporting.rst
> +:Original: Documentation/vm/free_page_reporting.rst
>   
>   :翻译:
>   
> diff --git a/Documentation/translations/zh_CN/vm/frontswap.rst b/Documentation/translations/zh_CN/vm/frontswap.rst
> index 3eb07870e2ef..98aa6f581ea7 100644
> --- a/Documentation/translations/zh_CN/vm/frontswap.rst
> +++ b/Documentation/translations/zh_CN/vm/frontswap.rst
> @@ -1,4 +1,4 @@
> -:Original: Documentation/vm/_free_page_reporting.rst
> +:Original: Documentation/vm/free_page_reporting.rst
>   
>   :翻译:
>   

[PATCH v2 08/20] docs: zh_CN/vm/zsmalloc.rst: fix a typo

[Mauro Carvalho Chehab]

typo:
	zs_malloc.rst -> zsmalloc.rst

Fixes: 6dbc3a5bdb46 ("docs/zh_CN: add vm zsmalloc translation")
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---

To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/

 Documentation/translations/zh_CN/vm/zsmalloc.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/translations/zh_CN/vm/zsmalloc.rst b/Documentation/translations/zh_CN/vm/zsmalloc.rst
index 29e9c70a8eb6..45a9b7ab2a51 100644
--- a/Documentation/translations/zh_CN/vm/zsmalloc.rst
+++ b/Documentation/translations/zh_CN/vm/zsmalloc.rst
@@ -1,4 +1,4 @@
-:Original: Documentation/vm/zs_malloc.rst
+:Original: Documentation/vm/zsmalloc.rst
 
 :翻译:
 
-- 
2.36.1

Re: [PATCH v2 08/20] docs: zh_CN/vm/zsmalloc.rst: fix a typo

[YanTeng Si]

在 2022/6/26 17:10, Mauro Carvalho Chehab 写道:
> typo:
> 	zs_malloc.rst -> zsmalloc.rst
>
> Fixes: 6dbc3a5bdb46 ("docs/zh_CN: add vm zsmalloc translation")
> Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>

Acked-by: Yanteng Si<siyanteng@loongson.cn>

Thanks,
Yanteng

> ---
>
> To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
> See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/
>
>   Documentation/translations/zh_CN/vm/zsmalloc.rst | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/translations/zh_CN/vm/zsmalloc.rst b/Documentation/translations/zh_CN/vm/zsmalloc.rst
> index 29e9c70a8eb6..45a9b7ab2a51 100644
> --- a/Documentation/translations/zh_CN/vm/zsmalloc.rst
> +++ b/Documentation/translations/zh_CN/vm/zsmalloc.rst
> @@ -1,4 +1,4 @@
> -:Original: Documentation/vm/zs_malloc.rst
> +:Original: Documentation/vm/zsmalloc.rst
>   
>   :翻译:
>   

[PATCH v2 09/20] docs: zh_CN/vm/index.rst: fix a broken reference

[Mauro Carvalho Chehab]

The reference is missing a .rst on it, causing its cross-reference
to not work.

Fixes: 9c3519d2b509 ("docs/zh_CN: add vm/index translation")
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---

To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/

 Documentation/translations/zh_CN/vm/index.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/translations/zh_CN/vm/index.rst b/Documentation/translations/zh_CN/vm/index.rst
index a1c6d529b6ff..81a9b782a427 100644
--- a/Documentation/translations/zh_CN/vm/index.rst
+++ b/Documentation/translations/zh_CN/vm/index.rst
@@ -15,7 +15,7 @@ Linux内存管理文档
 这是一个关于Linux内存管理（mm）子系统内部的文档集，其中有不同层次的细节，包括注释
 和邮件列表的回复，用于阐述数据结构和算法的基本情况。如果你正在寻找关于简单分配内存的建
 议，请参阅(Documentation/translations/zh_CN/core-api/memory-allocation.rst)。
-对于控制和调整指南，请参阅(Documentation/admin-guide/mm/index)。
+对于控制和调整指南，请参阅(Documentation/admin-guide/mm/index.rst)。
 TODO:待引用文档集被翻译完毕后请及时修改此处）
 
 .. toctree::
-- 
2.36.1

Re: [PATCH v2 09/20] docs: zh_CN/vm/index.rst: fix a broken reference

[YanTeng Si]

在 2022/6/26 17:10, Mauro Carvalho Chehab 写道:
> The reference is missing a .rst on it, causing its cross-reference
> to not work.
>
> Fixes: 9c3519d2b509 ("docs/zh_CN: add vm/index translation")
> Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
> ---
>
> To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
> See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/
>
>   Documentation/translations/zh_CN/vm/index.rst | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/translations/zh_CN/vm/index.rst b/Documentation/translations/zh_CN/vm/index.rst
> index a1c6d529b6ff..81a9b782a427 100644
> --- a/Documentation/translations/zh_CN/vm/index.rst
> +++ b/Documentation/translations/zh_CN/vm/index.rst
> @@ -15,7 +15,7 @@ Linux内存管理文档
>   这是一个关于Linux内存管理（mm）子系统内部的文档集，其中有不同层次的细节，包括注释
>   和邮件列表的回复，用于阐述数据结构和算法的基本情况。如果你正在寻找关于简单分配内存的建
>   议，请参阅(Documentation/translations/zh_CN/core-api/memory-allocation.rst)。
> -对于控制和调整指南，请参阅(Documentation/admin-guide/mm/index)。
> +对于控制和调整指南，请参阅(Documentation/admin-guide/mm/index.rst)。

Thanks, This index has been refactored.

<https://lore.kernel.org/all/35d10864fb9b57bf288d4efa5642f93a60079029.1655362610.git.siyanteng@loongson.cn/>


Thanks,

Yanteng

>   TODO:待引用文档集被翻译完毕后请及时修改此处）
>   
>   .. toctree::

[PATCH v2 10/20] Documentation: update watch_queue.rst references

[Mauro Carvalho Chehab]

Changeset f5461124d59b ("Documentation: move watch_queue to core-api")
renamed: Documentation/watch_queue.rst
to: Documentation/core-api/watch_queue.rst.

Update the cross-references accordingly.

Fixes: f5461124d59b ("Documentation: move watch_queue to core-api")
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---

To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/

 Documentation/security/keys/core.rst | 2 +-
 include/linux/watch_queue.h          | 2 +-
 init/Kconfig                         | 2 +-
 kernel/watch_queue.c                 | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/Documentation/security/keys/core.rst b/Documentation/security/keys/core.rst
index b3ed5c581034..811b905b56bf 100644
--- a/Documentation/security/keys/core.rst
+++ b/Documentation/security/keys/core.rst
@@ -1046,7 +1046,7 @@ The keyctl syscall functions are:
      "filter" is either NULL to remove a watch or a filter specification to
      indicate what events are required from the key.
 
-     See Documentation/watch_queue.rst for more information.
+     See Documentation/core-api/watch_queue.rst for more information.
 
      Note that only one watch may be emplaced for any particular { key,
      queue_fd } combination.
diff --git a/include/linux/watch_queue.h b/include/linux/watch_queue.h
index 3b9a40ae8bdb..fc6bba20273b 100644
--- a/include/linux/watch_queue.h
+++ b/include/linux/watch_queue.h
@@ -4,7 +4,7 @@
  * Copyright (C) 2020 Red Hat, Inc. All Rights Reserved.
  * Written by David Howells (dhowells@redhat.com)
  *
- * See Documentation/watch_queue.rst
+ * See Documentation/core-api/watch_queue.rst
  */
 
 #ifndef _LINUX_WATCH_QUEUE_H
diff --git a/init/Kconfig b/init/Kconfig
index ac8088850bdd..4dd1ee7358a3 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -432,7 +432,7 @@ config WATCH_QUEUE
 	  with watches for key/keyring change notifications and device
 	  notifications.
 
-	  See Documentation/watch_queue.rst
+	  See Documentation/core-api/watch_queue.rst
 
 config CROSS_MEMORY_ATTACH
 	bool "Enable process_vm_readv/writev syscalls"
diff --git a/kernel/watch_queue.c b/kernel/watch_queue.c
index 230038d4f908..869fea4fe26b 100644
--- a/kernel/watch_queue.c
+++ b/kernel/watch_queue.c
@@ -4,7 +4,7 @@
  * Copyright (C) 2020 Red Hat, Inc. All Rights Reserved.
  * Written by David Howells (dhowells@redhat.com)
  *
- * See Documentation/watch_queue.rst
+ * See Documentation/core-api/watch_queue.rst
  */
 
 #define pr_fmt(fmt) "watchq: " fmt
-- 
2.36.1

Re: [PATCH v2 10/20] Documentation: update watch_queue.rst references

[Randy Dunlap]

On 6/26/22 02:10, Mauro Carvalho Chehab wrote:
> Changeset f5461124d59b ("Documentation: move watch_queue to core-api")
> renamed: Documentation/watch_queue.rst
> to: Documentation/core-api/watch_queue.rst.
> 
> Update the cross-references accordingly.
> 
> Fixes: f5461124d59b ("Documentation: move watch_queue to core-api")
> Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
> Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>

Reviewed-by: Randy Dunlap <rdunlap@infradead.org>

Thanks.

> ---
> 
> To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
> See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/
> 
>  Documentation/security/keys/core.rst | 2 +-
>  include/linux/watch_queue.h          | 2 +-
>  init/Kconfig                         | 2 +-
>  kernel/watch_queue.c                 | 2 +-
>  4 files changed, 4 insertions(+), 4 deletions(-)


-- 
~Randy

[PATCH v2 11/20] Documentation: KVM: update s390-pv.rst reference

[Mauro Carvalho Chehab]

Changesets: daec8d408308 ("Documentation: KVM: add separate directories for architecture-specific documentation")
and: daec8d408308 ("Documentation: KVM: add separate directories for architecture-specific documentation")
renamed: Documentation/virt/kvm/s390-pv.rst
to: Documentation/virt/kvm/s390/s390-pv.rst.

Update its cross-reference accordingly.

Fixes: daec8d408308 ("Documentation: KVM: add separate directories for architecture-specific documentation")
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---

To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/

 Documentation/virt/kvm/s390/s390-pv-boot.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/virt/kvm/s390/s390-pv-boot.rst b/Documentation/virt/kvm/s390/s390-pv-boot.rst
index 73a6083cb5e7..96c48480a360 100644
--- a/Documentation/virt/kvm/s390/s390-pv-boot.rst
+++ b/Documentation/virt/kvm/s390/s390-pv-boot.rst
@@ -10,7 +10,7 @@ The memory of Protected Virtual Machines (PVMs) is not accessible to
 I/O or the hypervisor. In those cases where the hypervisor needs to
 access the memory of a PVM, that memory must be made accessible.
 Memory made accessible to the hypervisor will be encrypted. See
-Documentation/virt/kvm/s390-pv.rst for details."
+Documentation/virt/kvm/s390/s390-pv.rst for details."
 
 On IPL (boot) a small plaintext bootloader is started, which provides
 information about the encrypted components and necessary metadata to
-- 
2.36.1

[PATCH v2 12/20] Documentation: KVM: update amd-memory-encryption.rst references

[Mauro Carvalho Chehab]

Changeset daec8d408308 ("Documentation: KVM: add separate directories for architecture-specific documentation")
renamed: Documentation/virt/kvm/amd-memory-encryption.rst
to: Documentation/virt/kvm/x86/amd-memory-encryption.rst.

Update the cross-references accordingly.

Fixes: daec8d408308 ("Documentation: KVM: add separate directories for architecture-specific documentation")
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---

To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/

 Documentation/admin-guide/kernel-parameters.txt | 2 +-
 Documentation/security/secrets/coco.rst         | 2 +-
 Documentation/virt/kvm/api.rst                  | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
index f50e1fc6e51b..fc8cdc073764 100644
--- a/Documentation/admin-guide/kernel-parameters.txt
+++ b/Documentation/admin-guide/kernel-parameters.txt
@@ -3116,7 +3116,7 @@
 			mem_encrypt=on:		Activate SME
 			mem_encrypt=off:	Do not activate SME
 
-			Refer to Documentation/virt/kvm/amd-memory-encryption.rst
+			Refer to Documentation/virt/kvm/x86/amd-memory-encryption.rst
 			for details on when memory encryption can be activated.
 
 	mem_sleep_default=	[SUSPEND] Default system suspend mode:
diff --git a/Documentation/security/secrets/coco.rst b/Documentation/security/secrets/coco.rst
index 262e7abb1b24..087e2d1ae38b 100644
--- a/Documentation/security/secrets/coco.rst
+++ b/Documentation/security/secrets/coco.rst
@@ -98,6 +98,6 @@ References
 
 See [sev-api-spec]_ for more info regarding SEV ``LAUNCH_SECRET`` operation.
 
-.. [sev] Documentation/virt/kvm/amd-memory-encryption.rst
+.. [sev] Documentation/virt/kvm/x86/amd-memory-encryption.rst
 .. [secrets-coco-abi] Documentation/ABI/testing/securityfs-secrets-coco
 .. [sev-api-spec] https://www.amd.com/system/files/TechDocs/55766_SEV-KM_API_Specification.pdf
diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst
index 84c486ce6279..9260152c37cb 100644
--- a/Documentation/virt/kvm/api.rst
+++ b/Documentation/virt/kvm/api.rst
@@ -4677,7 +4677,7 @@ encrypted VMs.
 
 Currently, this ioctl is used for issuing Secure Encrypted Virtualization
 (SEV) commands on AMD Processors. The SEV commands are defined in
-Documentation/virt/kvm/amd-memory-encryption.rst.
+Documentation/virt/kvm/x86/amd-memory-encryption.rst.
 
 4.111 KVM_MEMORY_ENCRYPT_REG_REGION
 -----------------------------------
-- 
2.36.1

[PATCH v2 13/20] Documentation: KVM: update msr.rst reference

[Mauro Carvalho Chehab]

Changeset daec8d408308 ("Documentation: KVM: add separate directories for architecture-specific documentation")
renamed: Documentation/virt/kvm/msr.rst
to: Documentation/virt/kvm/x86/msr.rst.

Update its cross-reference accordingly.

Fixes: daec8d408308 ("Documentation: KVM: add separate directories for architecture-specific documentation")
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---

To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/

 Documentation/virt/kvm/api.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst
index 9260152c37cb..41afd1125cb1 100644
--- a/Documentation/virt/kvm/api.rst
+++ b/Documentation/virt/kvm/api.rst
@@ -7894,7 +7894,7 @@ architecture-specific interfaces.  This capability and the architecture-
 specific interfaces must be consistent, i.e. if one says the feature
 is supported, than the other should as well and vice versa.  For arm64
 see Documentation/virt/kvm/devices/vcpu.rst "KVM_ARM_VCPU_PVTIME_CTRL".
-For x86 see Documentation/virt/kvm/msr.rst "MSR_KVM_STEAL_TIME".
+For x86 see Documentation/virt/kvm/x86/msr.rst "MSR_KVM_STEAL_TIME".
 
 8.25 KVM_CAP_S390_DIAG318
 -------------------------
-- 
2.36.1

[PATCH v2 14/20] Documentation: KVM: update s390-diag.rst reference

[Mauro Carvalho Chehab]

Changeset daec8d408308 ("Documentation: KVM: add separate directories for architecture-specific documentation")
renamed: Documentation/virt/kvm/s390-diag.rst
to: Documentation/virt/kvm/s390/s390-diag.rst.

Update its cross-reference accordingly.

Fixes: daec8d408308 ("Documentation: KVM: add separate directories for architecture-specific documentation")
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---

To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/

 Documentation/virt/kvm/x86/hypercalls.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/virt/kvm/x86/hypercalls.rst b/Documentation/virt/kvm/x86/hypercalls.rst
index e56fa8b9cfca..10db7924720f 100644
--- a/Documentation/virt/kvm/x86/hypercalls.rst
+++ b/Documentation/virt/kvm/x86/hypercalls.rst
@@ -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.rst.
+  refer to Documentation/virt/kvm/s390/s390-diag.rst.
 
 PowerPC:
   It uses R3-R10 and hypercall number in R11. R4-R11 are used as output registers.
-- 
2.36.1

[PATCH v2 15/20] objtool: update objtool.txt references

[Mauro Carvalho Chehab]

Changeset a8e35fece49b ("objtool: Update documentation")
renamed: tools/objtool/Documentation/stack-validation.txt
to: tools/objtool/Documentation/objtool.txt.

Update the cross-references accordingly.

Fixes: a8e35fece49b ("objtool: Update documentation")
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---

To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/

 Documentation/x86/orc-unwinder.rst | 2 +-
 include/linux/objtool.h            | 2 +-
 lib/Kconfig.debug                  | 2 +-
 tools/include/linux/objtool.h      | 2 +-
 tools/objtool/check.c              | 2 +-
 5 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/Documentation/x86/orc-unwinder.rst b/Documentation/x86/orc-unwinder.rst
index 9a66a88be765..cdb257015bd9 100644
--- a/Documentation/x86/orc-unwinder.rst
+++ b/Documentation/x86/orc-unwinder.rst
@@ -140,7 +140,7 @@ Unwinder implementation details
 
 Objtool generates the ORC data by integrating with the compile-time
 stack metadata validation feature, which is described in detail in
-tools/objtool/Documentation/stack-validation.txt.  After analyzing all
+tools/objtool/Documentation/objtool.txt.  After analyzing all
 the code paths of a .o file, it creates an array of orc_entry structs,
 and a parallel array of instruction addresses associated with those
 structs, and writes them to the .orc_unwind and .orc_unwind_ip sections
diff --git a/include/linux/objtool.h b/include/linux/objtool.h
index 15b940ec1eac..1c769cddb42a 100644
--- a/include/linux/objtool.h
+++ b/include/linux/objtool.h
@@ -62,7 +62,7 @@ struct unwind_hint {
  * It should only be used in special cases where you're 100% sure it won't
  * affect the reliability of frame pointers and kernel stack traces.
  *
- * For more information, see tools/objtool/Documentation/stack-validation.txt.
+ * For more information, see tools/objtool/Documentation/objtool.txt.
  */
 #define STACK_FRAME_NON_STANDARD(func) \
 	static void __used __section(".discard.func_stack_frame_non_standard") \
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 3da5f9acb966..3025347bb433 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -498,7 +498,7 @@ config STACK_VALIDATION
 	  runtime stack traces are more reliable.
 
 	  For more information, see
-	  tools/objtool/Documentation/stack-validation.txt.
+	  tools/objtool/Documentation/objtool.txt.
 
 config NOINSTR_VALIDATION
 	bool
diff --git a/tools/include/linux/objtool.h b/tools/include/linux/objtool.h
index 15b940ec1eac..1c769cddb42a 100644
--- a/tools/include/linux/objtool.h
+++ b/tools/include/linux/objtool.h
@@ -62,7 +62,7 @@ struct unwind_hint {
  * It should only be used in special cases where you're 100% sure it won't
  * affect the reliability of frame pointers and kernel stack traces.
  *
- * For more information, see tools/objtool/Documentation/stack-validation.txt.
+ * For more information, see tools/objtool/Documentation/objtool.txt.
  */
 #define STACK_FRAME_NON_STANDARD(func) \
 	static void __used __section(".discard.func_stack_frame_non_standard") \
diff --git a/tools/objtool/check.c b/tools/objtool/check.c
index 864bb9dd3584..970844ceecdc 100644
--- a/tools/objtool/check.c
+++ b/tools/objtool/check.c
@@ -3190,7 +3190,7 @@ static struct instruction *next_insn_to_validate(struct objtool_file *file,
  * Follow the branch starting at the given instruction, and recursively follow
  * any other branches (jumps).  Meanwhile, track the frame pointer state at
  * each instruction and validate all the rules described in
- * tools/objtool/Documentation/stack-validation.txt.
+ * tools/objtool/Documentation/objtool.txt.
  */
 static int validate_branch(struct objtool_file *file, struct symbol *func,
 			   struct instruction *insn, struct insn_state state)
-- 
2.36.1

[PATCH v2 16/20] arch: m68k: q40: README: drop references to IDE driver

[Mauro Carvalho Chehab]

Since IDE support was deleted by Christoph Hellwig <hch@lst.de>,
Jun 16 2021, drop the left-over from README file, updating the
documentation to point to ata/pata_falcon.c.

Fixes: 44b1fbc0f5f3 ("m68k/q40: Replace q40ide driver with pata_falcon and falconide")
Fixes: b7fb14d3ac63 ("ide: remove the legacy ide driver")
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---

To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/

 arch/m68k/q40/README | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/arch/m68k/q40/README b/arch/m68k/q40/README
index a4991d2d8af6..9760e9081f6f 100644
--- a/arch/m68k/q40/README
+++ b/arch/m68k/q40/README
@@ -30,11 +30,10 @@ drivers used by the Q40, apart from the very obvious (console etc.):
 		     genrtc.c		# RTC
 		char/joystick/*		# most of this should work, not
 				        # in default config.in
-	        block/q40ide.c		# startup for ide
-		      ide*		# see Documentation/ide/ide.rst
-		      floppy.c		# normal PC driver, DMA emu in asm/floppy.h
+	        block/floppy.c		# normal PC driver, DMA emu in asm/floppy.h
 					# and arch/m68k/kernel/entry.S
 					# see drivers/block/README.fd
+		ata/pata_falcon.c
 		net/ne.c
 		video/q40fb.c
 		parport/*
-- 
2.36.1

Re: [PATCH v2 16/20] arch: m68k: q40: README: drop references to IDE driver

[Geert Uytterhoeven]

On Sun, Jun 26, 2022 at 11:11 AM Mauro Carvalho Chehab
<mchehab@kernel.org> wrote:
> Since IDE support was deleted by Christoph Hellwig <hch@lst.de>,
> Jun 16 2021, drop the left-over from README file, updating the
> documentation to point to ata/pata_falcon.c.
>
> Fixes: 44b1fbc0f5f3 ("m68k/q40: Replace q40ide driver with pata_falcon and falconide")
> Fixes: b7fb14d3ac63 ("ide: remove the legacy ide driver")
> Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>

Reviewed-by: Geert Uytterhoeven <geert@linux-m68k.org>
Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

[PATCH v2 17/20] tegra194-hte.rst: fix reference to its binding

[Mauro Carvalho Chehab]

The binding directory for hte was renamed. Update references accordingly.

Fixes: af583852d2ef ("dt-bindings: Renamed hte directory to timestamp")
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---

To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/

 Documentation/driver-api/hte/tegra194-hte.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/driver-api/hte/tegra194-hte.rst b/Documentation/driver-api/hte/tegra194-hte.rst
index 41983e04d2a0..d29b7fe86f31 100644
--- a/Documentation/driver-api/hte/tegra194-hte.rst
+++ b/Documentation/driver-api/hte/tegra194-hte.rst
@@ -37,7 +37,7 @@ LIC (Legacy Interrupt Controller) IRQ GTE
 
 This GTE instance timestamps LIC IRQ lines in real time. There are 352 IRQ
 lines which this instance can add timestamps to in real time. The hte
-devicetree binding described at ``Documentation/devicetree/bindings/hte/``
+devicetree binding described at ``Documentation/devicetree/bindings/timestamp``
 provides an example of how a consumer can request an IRQ line. Since it is a
 one-to-one mapping with IRQ GTE provider, consumers can simply specify the IRQ
 number that they are interested in. There is no userspace consumer support for
-- 
2.36.1

Re: [PATCH v2 17/20] tegra194-hte.rst: fix reference to its binding

[Dipen Patel]

On 6/26/22 2:11 AM, Mauro Carvalho Chehab wrote:
> The binding directory for hte was renamed. Update references accordingly.
>
> Fixes: af583852d2ef ("dt-bindings: Renamed hte directory to timestamp")
> Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
> ---
>
> To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
> See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/
>
>  Documentation/driver-api/hte/tegra194-hte.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/driver-api/hte/tegra194-hte.rst b/Documentation/driver-api/hte/tegra194-hte.rst
> index 41983e04d2a0..d29b7fe86f31 100644
> --- a/Documentation/driver-api/hte/tegra194-hte.rst
> +++ b/Documentation/driver-api/hte/tegra194-hte.rst
> @@ -37,7 +37,7 @@ LIC (Legacy Interrupt Controller) IRQ GTE
>  
>  This GTE instance timestamps LIC IRQ lines in real time. There are 352 IRQ
>  lines which this instance can add timestamps to in real time. The hte
> -devicetree binding described at ``Documentation/devicetree/bindings/hte/``
> +devicetree binding described at ``Documentation/devicetree/bindings/timestamp``
>  provides an example of how a consumer can request an IRQ line. Since it is a
>  one-to-one mapping with IRQ GTE provider, consumers can simply specify the IRQ
>  number that they are interested in. There is no userspace consumer support for

Reviewed-by: Dipen Patel <dipenp@nvidia.com>

Re: [PATCH v2 17/20] tegra194-hte.rst: fix reference to its binding

[Thierry Reding]

[-- Attachment #1: Type: text/plain, Size: 1806 bytes --]

On Mon, Jun 27, 2022 at 10:14:45AM -0700, Dipen Patel wrote:
> On 6/26/22 2:11 AM, Mauro Carvalho Chehab wrote:
> > The binding directory for hte was renamed. Update references accordingly.
> >
> > Fixes: af583852d2ef ("dt-bindings: Renamed hte directory to timestamp")
> > Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
> > ---
> >
> > To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
> > See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/
> >
> >  Documentation/driver-api/hte/tegra194-hte.rst | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/Documentation/driver-api/hte/tegra194-hte.rst b/Documentation/driver-api/hte/tegra194-hte.rst
> > index 41983e04d2a0..d29b7fe86f31 100644
> > --- a/Documentation/driver-api/hte/tegra194-hte.rst
> > +++ b/Documentation/driver-api/hte/tegra194-hte.rst
> > @@ -37,7 +37,7 @@ LIC (Legacy Interrupt Controller) IRQ GTE
> >  
> >  This GTE instance timestamps LIC IRQ lines in real time. There are 352 IRQ
> >  lines which this instance can add timestamps to in real time. The hte
> > -devicetree binding described at ``Documentation/devicetree/bindings/hte/``
> > +devicetree binding described at ``Documentation/devicetree/bindings/timestamp``
> >  provides an example of how a consumer can request an IRQ line. Since it is a
> >  one-to-one mapping with IRQ GTE provider, consumers can simply specify the IRQ
> >  number that they are interested in. There is no userspace consumer support for
> 
> Reviewed-by: Dipen Patel <dipenp@nvidia.com>

Hi Jonathan,

I think you'll need to pick this one up since it applies on top of your
earlier patch that moves this documentation into driver-api/.

Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[PATCH v2 18/20] dt-bindings: mfd: update dlg,da9063.yaml reference

[Mauro Carvalho Chehab]

Changeset 441613662db7 ("dt-bindings: mfd: Convert da9063 to yaml")
renamed: Documentation/devicetree/bindings/mfd/da9063.txt
to: Documentation/devicetree/bindings/mfd/dlg,da9063.yaml.

Update its cross-reference accordingly.

Fixes: 441613662db7 ("dt-bindings: mfd: Convert da9063 to yaml")
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---

To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/

 Documentation/devicetree/bindings/input/da9062-onkey.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/devicetree/bindings/input/da9062-onkey.txt b/Documentation/devicetree/bindings/input/da9062-onkey.txt
index 5f9fbc68e58a..e5eef59a93dc 100644
--- a/Documentation/devicetree/bindings/input/da9062-onkey.txt
+++ b/Documentation/devicetree/bindings/input/da9062-onkey.txt
@@ -2,7 +2,7 @@
 
 This module is part of the DA9061/DA9062/DA9063. For more details about entire
 DA9062 and DA9061 chips see Documentation/devicetree/bindings/mfd/da9062.txt
-For DA9063 see Documentation/devicetree/bindings/mfd/da9063.txt
+For DA9063 see Documentation/devicetree/bindings/mfd/dlg,da9063.yaml
 
 This module provides the KEY_POWER event.
 
-- 
2.36.1

Re: [PATCH v2 18/20] dt-bindings: mfd: update dlg,da9063.yaml reference

[Conor.Dooley]

On 26/06/2022 10:11, Mauro Carvalho Chehab wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> Changeset 441613662db7 ("dt-bindings: mfd: Convert da9063 to yaml")
> renamed: Documentation/devicetree/bindings/mfd/da9063.txt
> to: Documentation/devicetree/bindings/mfd/dlg,da9063.yaml.
> 
> Update its cross-reference accordingly.

Hey Mauro,
Thanks for the patch.
Acked-by: Conor Dooley <conor.dooley@microchip.com>

> 
> Fixes: 441613662db7 ("dt-bindings: mfd: Convert da9063 to yaml")
> Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
> ---
> 
> To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
> See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/
> 
>   Documentation/devicetree/bindings/input/da9062-onkey.txt | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/devicetree/bindings/input/da9062-onkey.txt b/Documentation/devicetree/bindings/input/da9062-onkey.txt
> index 5f9fbc68e58a..e5eef59a93dc 100644
> --- a/Documentation/devicetree/bindings/input/da9062-onkey.txt
> +++ b/Documentation/devicetree/bindings/input/da9062-onkey.txt
> @@ -2,7 +2,7 @@
> 
>   This module is part of the DA9061/DA9062/DA9063. For more details about entire
>   DA9062 and DA9061 chips see Documentation/devicetree/bindings/mfd/da9062.txt
> -For DA9063 see Documentation/devicetree/bindings/mfd/da9063.txt
> +For DA9063 see Documentation/devicetree/bindings/mfd/dlg,da9063.yaml
> 
>   This module provides the KEY_POWER event.
> 
> --
> 2.36.1
> 

Re: [PATCH v2 18/20] dt-bindings: mfd: update dlg,da9063.yaml reference

[Rob Herring]

On Sun, 26 Jun 2022 10:11:04 +0100, Mauro Carvalho Chehab wrote:
> Changeset 441613662db7 ("dt-bindings: mfd: Convert da9063 to yaml")
> renamed: Documentation/devicetree/bindings/mfd/da9063.txt
> to: Documentation/devicetree/bindings/mfd/dlg,da9063.yaml.
> 
> Update its cross-reference accordingly.
> 
> Fixes: 441613662db7 ("dt-bindings: mfd: Convert da9063 to yaml")
> Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
> ---
> 
> To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
> See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/
> 
>  Documentation/devicetree/bindings/input/da9062-onkey.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 

Acked-by: Rob Herring <robh@kernel.org>

[PATCH v2 19/20] MAINTAINERS: update nvidia,tegra20-host1x.yaml reference

[Mauro Carvalho Chehab]

Changeset fd27de58b0ad ("dt-bindings: display: tegra: Convert to json-schema")
renamed: Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-host1x.txt
to: Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-host1x.yaml.

Update its cross-reference accordingly.

Fixes: fd27de58b0ad ("dt-bindings: display: tegra: Convert to json-schema")
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---

To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/

 MAINTAINERS | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index 7c9187635801..cd3f4964c14a 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -6787,7 +6787,7 @@ L:	dri-devel@lists.freedesktop.org
 L:	linux-tegra@vger.kernel.org
 S:	Supported
 T:	git git://anongit.freedesktop.org/tegra/linux.git
-F:	Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-host1x.txt
+F:	Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-host1x.yaml
 F:	Documentation/devicetree/bindings/gpu/host1x/
 F:	drivers/gpu/drm/tegra/
 F:	drivers/gpu/host1x/
@@ -19790,7 +19790,7 @@ M:	Sowjanya Komatineni <skomatineni@nvidia.com>
 L:	linux-media@vger.kernel.org
 L:	linux-tegra@vger.kernel.org
 S:	Maintained
-F:	Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-host1x.txt
+F:	Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-host1x.yaml
 F:	drivers/staging/media/tegra-video/
 
 TEGRA XUSB PADCTL DRIVER
-- 
2.36.1

[PATCH v2 20/20] MAINTAINERS: fix cross references to mfd/dlg,da9063.yaml

[Mauro Carvalho Chehab]

The entry forgot to add "dlg," to the file pattern.

Fixes: 441613662db7 ("dt-bindings: mfd: Convert da9063 to yaml")
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---

To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/

 MAINTAINERS | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index cd3f4964c14a..6acae3a340cb 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -5886,7 +5886,7 @@ W:	http://www.dialog-semiconductor.com/products
 F:	Documentation/devicetree/bindings/input/da90??-onkey.txt
 F:	Documentation/devicetree/bindings/input/dlg,da72??.txt
 F:	Documentation/devicetree/bindings/mfd/da90*.txt
-F:	Documentation/devicetree/bindings/mfd/da90*.yaml
+F:	Documentation/devicetree/bindings/mfd/dlg,da90*.yaml
 F:	Documentation/devicetree/bindings/regulator/dlg,da9*.yaml
 F:	Documentation/devicetree/bindings/regulator/da92*.txt
 F:	Documentation/devicetree/bindings/regulator/slg51000.txt
-- 
2.36.1

Re: [PATCH v2 20/20] MAINTAINERS: fix cross references to mfd/dlg,da9063.yaml

[Conor.Dooley]

On 26/06/2022 10:11, Mauro Carvalho Chehab wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> The entry forgot to add "dlg," to the file pattern.

Hey Mauro,
Thanks for the patch, but this one should not be needed.
Lukas has already sent a fix for the MAINTAINERS entry.
Thanks,
Conor.

> 
> Fixes: 441613662db7 ("dt-bindings: mfd: Convert da9063 to yaml")
> Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
> ---
> 
> To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
> See [PATCH v2 00/20] at: https://lore.kernel.org/all/cover.1656234456.git.mchehab@kernel.org/
> 
>   MAINTAINERS | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index cd3f4964c14a..6acae3a340cb 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -5886,7 +5886,7 @@ W:        http://www.dialog-semiconductor.com/products
>   F:     Documentation/devicetree/bindings/input/da90??-onkey.txt
>   F:     Documentation/devicetree/bindings/input/dlg,da72??.txt
>   F:     Documentation/devicetree/bindings/mfd/da90*.txt
> -F:     Documentation/devicetree/bindings/mfd/da90*.yaml
> +F:     Documentation/devicetree/bindings/mfd/dlg,da90*.yaml
>   F:     Documentation/devicetree/bindings/regulator/dlg,da9*.yaml
>   F:     Documentation/devicetree/bindings/regulator/da92*.txt
>   F:     Documentation/devicetree/bindings/regulator/slg51000.txt
> --
> 2.36.1
> 

Re: [PATCH v2 00/20] Update Documentation/ cross-references

[Jonathan Corbet]

Mauro Carvalho Chehab <mchehab@kernel.org> writes:

> Fix most broken documentation file cross references on next-20220624.
>
> After this series, only 3 references will be broken:

OK, I've applied everything except parts 4, 9, and 20.

Thanks,

jon

Re: [PATCH v2 00/20] Update Documentation/ cross-references

[Jonathan Corbet]

Mauro Carvalho Chehab <mchehab@kernel.org> writes:

> Fix most broken documentation file cross references on next-20220624.
>
> After this series, only 3 references will be broken:

OK, I've applied everything except parts 4, 9, and 20.

Thanks,

jon

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv