workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Breno Leitao <leitao@debian.org>,
	Akinobu Mita <akinobu.mita@gmail.com>,
	Federico Vaga <federico.vaga@vaga.pv.it>,
	Akira Yokosawa <akiyks@gmail.com>,
	Carlos Bilbao <carlos.bilbao.osdev@gmail.com>,
	Avadhut Naik <avadhut.naik@amd.com>, Alex Shi <alexs@kernel.org>,
	Yanteng Si <siyanteng@loongson.cn>,
	Hu Haowen <2023002089@link.tyut.edu.cn>,
	Jens Axboe <axboe@kernel.dk>, Kees Cook <kees@kernel.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Alim Akhtar <alim.akhtar@samsung.com>,
	Avri Altman <avri.altman@wdc.com>,
	Bart Van Assche <bvanassche@acm.org>,
	"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: leit@meta.com, "Paul E. McKenney" <paulmck@kernel.org>,
	Thomas Huth <thuth@redhat.com>,
	"Borislav Petkov (AMD)" <bp@alien8.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Xiongwei Song <xiongwei.song@windriver.com>,
	Ard Biesheuvel <ardb@kernel.org>, John Moon <john@jmoon.dev>,
	Vegard Nossum <vegard.nossum@oracle.com>,
	Miguel Ojeda <ojeda@kernel.org>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>,
	SeongJae Park <sj@kernel.org>, "Ran.Park" <ranpark@foxmail.com>,
	Tiezhu Yang <yangtiezhu@loongson.cn>,
	Remington Brasga <rbrasga@uci.edu>,
	Damien Le Moal <dlemoal@kernel.org>,
	Hannes Reinecke <hare@suse.de>,
	Chaitanya Kulkarni <kch@nvidia.com>,
	Johannes Thumshirn <johannes.thumshirn@wdc.com>,
	Zhu Yanjun <yanjun.zhu@linux.dev>,
	John Garry <john.g.garry@oracle.com>,
	Chengming Zhou <zhouchengming@bytedance.com>,
	Yu Kuai <yukuai3@huawei.com>,
	Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
	Vlastimil Babka <vbabka@suse.cz>,
	"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	"open list:DOCUMENTATION PROCESS" <workflows@vger.kernel.org>,
	"open list:BLOCK LAYER" <linux-block@vger.kernel.org>,
	"open list:UNIVERSAL FLASH STORAGE HOST CONTROLLER DRIVER"
	<linux-scsi@vger.kernel.org>,
	"open list:GENERIC INCLUDE/ASM HEADER FILES"
	<linux-arch@vger.kernel.org>
Subject: Re: [PATCH v2] docs: Move fault injection section to dev-tools
Date: Thu, 05 Sep 2024 13:40:17 -0600	[thread overview]
Message-ID: <87ttethota.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20240902125421.569668-1-leitao@debian.org>

Breno Leitao <leitao@debian.org> writes:

> Fault injection is a development tool, and should be under dev-tools
> section.
>
> Suggested-by: Jonathan Corbet <corbet@lwn.net>
> Signed-off-by: Breno Leitao <leitao@debian.org>
> ---
> Changelog:
>
> v2:
>   * Fixed a remaining file pointing to the wrong file, as reported by
>     kernel test robot:
> 	* https://lore.kernel.org/all/202408312350.DEf53QzI-lkp@intel.com/ 
>
> v1:
>   * https://lore.kernel.org/all/20240830174502.3732959-1-leitao@debian.org/
>
>  Documentation/admin-guide/kernel-parameters.txt              | 2 +-
>  .../{ => dev-tools}/fault-injection/fault-injection.rst      | 0
>  Documentation/{ => dev-tools}/fault-injection/index.rst      | 0
>  .../fault-injection/notifier-error-inject.rst                | 0
>  .../{ => dev-tools}/fault-injection/nvme-fault-injection.rst | 0
>  .../{ => dev-tools}/fault-injection/provoke-crashes.rst      | 0
>  Documentation/dev-tools/index.rst                            | 1 +
>  Documentation/index.rst                                      | 1 -
>  Documentation/process/4.Coding.rst                           | 2 +-
>  Documentation/process/submit-checklist.rst                   | 2 +-
>  Documentation/translations/it_IT/process/4.Coding.rst        | 2 +-
>  .../translations/it_IT/process/submit-checklist.rst          | 2 +-
>  Documentation/translations/ja_JP/SubmitChecklist             | 2 +-
>  .../translations/sp_SP/process/submit-checklist.rst          | 2 +-
>  Documentation/translations/zh_CN/index.rst                   | 2 +-
>  Documentation/translations/zh_CN/process/4.Coding.rst        | 2 +-
>  .../translations/zh_CN/process/submit-checklist.rst          | 2 +-
>  Documentation/translations/zh_TW/index.rst                   | 2 +-
>  Documentation/translations/zh_TW/process/4.Coding.rst        | 2 +-
>  .../translations/zh_TW/process/submit-checklist.rst          | 2 +-
>  MAINTAINERS                                                  | 2 +-
>  drivers/block/null_blk/main.c                                | 2 +-
>  drivers/misc/lkdtm/core.c                                    | 2 +-
>  drivers/ufs/core/ufs-fault-injection.c                       | 2 +-
>  include/asm-generic/error-injection.h                        | 5 +++--
>  include/linux/fault-inject.h                                 | 2 +-
>  lib/Kconfig.debug                                            | 4 ++--
>  tools/testing/fault-injection/failcmd.sh                     | 2 +-
>  28 files changed, 25 insertions(+), 24 deletions(-)
>  rename Documentation/{ => dev-tools}/fault-injection/fault-injection.rst (100%)
>  rename Documentation/{ => dev-tools}/fault-injection/index.rst (100%)
>  rename Documentation/{ => dev-tools}/fault-injection/notifier-error-inject.rst (100%)
>  rename Documentation/{ => dev-tools}/fault-injection/nvme-fault-injection.rst (100%)
>  rename Documentation/{ => dev-tools}/fault-injection/provoke-crashes.rst (100%)

Applied, thanks.

jon

      parent reply	other threads:[~2024-09-05 19:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-02 12:53 Breno Leitao
2024-09-03  1:23 ` Alex Shi
2024-09-04 20:06 ` Carlos Bilbao
2024-09-05 19:40 ` Jonathan Corbet [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ttethota.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=2023002089@link.tyut.edu.cn \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=akinobu.mita@gmail.com \
    --cc=akiyks@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexs@kernel.org \
    --cc=alim.akhtar@samsung.com \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=avadhut.naik@amd.com \
    --cc=avri.altman@wdc.com \
    --cc=axboe@kernel.dk \
    --cc=bp@alien8.de \
    --cc=bvanassche@acm.org \
    --cc=carlos.bilbao.osdev@gmail.com \
    --cc=dlemoal@kernel.org \
    --cc=federico.vaga@vaga.pv.it \
    --cc=gregkh@linuxfoundation.org \
    --cc=hare@suse.de \
    --cc=johannes.thumshirn@wdc.com \
    --cc=john.g.garry@oracle.com \
    --cc=john@jmoon.dev \
    --cc=kch@nvidia.com \
    --cc=kees@kernel.org \
    --cc=leit@meta.com \
    --cc=leitao@debian.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=ojeda@kernel.org \
    --cc=paulmck@kernel.org \
    --cc=ranpark@foxmail.com \
    --cc=rbrasga@uci.edu \
    --cc=shinichiro.kawasaki@wdc.com \
    --cc=siyanteng@loongson.cn \
    --cc=sj@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=thuth@redhat.com \
    --cc=vbabka@suse.cz \
    --cc=vegard.nossum@oracle.com \
    --cc=workflows@vger.kernel.org \
    --cc=wsa+renesas@sang-engineering.com \
    --cc=xiongwei.song@windriver.com \
    --cc=yangtiezhu@loongson.cn \
    --cc=yanjun.zhu@linux.dev \
    --cc=yukuai3@huawei.com \
    --cc=zhouchengming@bytedance.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox