All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Jonathan Corbet <corbet@lwn.net>, Jeff Dike <jdike@addtoit.com>,
	Richard Weinberger <richard@nod.at>,
	linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
	linux-doc@vger.kernel.org,
	user-mode-linux-devel@lists.sourceforge.net,
	user-mode-linux-user@lists.sourceforge.net
Subject: Re: [PATCH] Documentation: Update path to sysrq.txt
Date: Fri, 24 Feb 2017 06:52:02 -0300	[thread overview]
Message-ID: <20170224065202.31b60514@vento.lan> (raw)
In-Reply-To: <20170224084214.6889-1-krzk@kernel.org>

Em Fri, 24 Feb 2017 10:42:14 +0200
Krzysztof Kozlowski <krzk@kernel.org> escreveu:

> Commit 9d85025b0418 ("docs-rst: create an user's manual book") moved the
> sysrq.txt leaving old paths in the kernel docs.
> 
> Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
Reviewed-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>

> ---
>  Documentation/media/v4l-drivers/bttv.rst          | 2 +-
>  Documentation/s390/Debugging390.txt               | 2 +-
>  Documentation/sysctl/kernel.txt                   | 2 +-
>  Documentation/virtual/uml/UserModeLinux-HOWTO.txt | 6 +++---
>  4 files changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/Documentation/media/v4l-drivers/bttv.rst b/Documentation/media/v4l-drivers/bttv.rst
> index bc63b12efafd..195ccaac2816 100644
> --- a/Documentation/media/v4l-drivers/bttv.rst
> +++ b/Documentation/media/v4l-drivers/bttv.rst
> @@ -312,7 +312,7 @@ information out of a register+stack dump printed by the kernel on
>  protection faults (so-called "kernel oops").
>  
>  If you run into some kind of deadlock, you can try to dump a call trace
> -for each process using sysrq-t (see Documentation/sysrq.txt).
> +for each process using sysrq-t (see Documentation/admin-guide/sysrq.rst).
>  This way it is possible to figure where *exactly* some process in "D"
>  state is stuck.
>  
> diff --git a/Documentation/s390/Debugging390.txt b/Documentation/s390/Debugging390.txt
> index 3df8babcdc41..5ae7f868a007 100644
> --- a/Documentation/s390/Debugging390.txt
> +++ b/Documentation/s390/Debugging390.txt
> @@ -2116,7 +2116,7 @@ The sysrq key reading is very picky ( I have to type the keys in an
>  This is particularly useful for syncing disks unmounting & rebooting
>  if the machine gets partially hung.
>  
> -Read Documentation/sysrq.txt for more info
> +Read Documentation/admin-guide/sysrq.rst for more info
>  
>  References:
>  ===========
> diff --git a/Documentation/sysctl/kernel.txt b/Documentation/sysctl/kernel.txt
> index a32b4b748644..bac23c198360 100644
> --- a/Documentation/sysctl/kernel.txt
> +++ b/Documentation/sysctl/kernel.txt
> @@ -85,7 +85,7 @@ show up in /proc/sys/kernel:
>  - softlockup_all_cpu_backtrace
>  - soft_watchdog
>  - stop-a                      [ SPARC only ]
> -- sysrq                       ==> Documentation/sysrq.txt
> +- sysrq                       ==> Documentation/admin-guide/sysrq.rst
>  - sysctl_writes_strict
>  - tainted
>  - threads-max
> diff --git a/Documentation/virtual/uml/UserModeLinux-HOWTO.txt b/Documentation/virtual/uml/UserModeLinux-HOWTO.txt
> index f4099ca6b483..87b80f589e1c 100644
> --- a/Documentation/virtual/uml/UserModeLinux-HOWTO.txt
> +++ b/Documentation/virtual/uml/UserModeLinux-HOWTO.txt
> @@ -2401,9 +2401,9 @@
>  
>    This takes one argument, which is a single letter.  It calls the
>    generic kernel's SysRq driver, which does whatever is called for by
> -  that argument.  See the SysRq documentation in Documentation/sysrq.txt
> -  in your favorite kernel tree to see what letters are valid and what
> -  they do.
> +  that argument.  See the SysRq documentation in
> +  Documentation/admin-guide/sysrq.rst in your favorite kernel tree to
> +  see what letters are valid and what they do.
>  
>  
>  



Thanks,
Mauro

  reply	other threads:[~2017-02-24  9:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-24  8:42 [PATCH] Documentation: Update path to sysrq.txt Krzysztof Kozlowski
2017-02-24  9:52 ` Mauro Carvalho Chehab [this message]
2017-03-03 22:48 ` Jonathan Corbet

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=20170224065202.31b60514@vento.lan \
    --to=mchehab@s-opensource.com \
    --cc=corbet@lwn.net \
    --cc=heiko.carstens@de.ibm.com \
    --cc=jdike@addtoit.com \
    --cc=krzk@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=richard@nod.at \
    --cc=schwidefsky@de.ibm.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    --cc=user-mode-linux-user@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.