From: Guenter Roeck <linux@roeck-us.net>
To: Tom Saeger <tom.saeger@oracle.com>
Cc: Jonathan Corbet <corbet@lwn.net>, Jan Kara <jack@suse.cz>,
Amir Goldstein <amir73il@gmail.com>,
Jimmy Vance <jimmy.vance@hpe.com>,
Wim Van Sebroeck <wim@iguana.be>,
linux-doc@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [7/8] Documentation: fix selftests related file refs
Date: Sun, 22 Oct 2017 09:23:46 -0700 [thread overview]
Message-ID: <20171022162346.GA13195@roeck-us.net> (raw)
In-Reply-To: <d4ae0439fc28ad274822f62f46b6230114e3e2da.1507838726.git.tom.saeger@oracle.com>
On Thu, Oct 12, 2017 at 03:24:10PM -0500, Tom Saeger wrote:
> Make refs to selftests files valid including:
> - watchdog-test.c
> - dnotify_test.c
>
> Signed-off-by: Tom Saeger <tom.saeger@oracle.com>
> Signed-off-by: Jerry Hoemann <jerry.hoemann@hpe.com>
That should have been a Reviewed-by: for the hpwdt code.
Otherwise
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> ---
> Documentation/filesystems/dnotify.txt | 2 +-
> Documentation/watchdog/hpwdt.txt | 2 +-
> Documentation/watchdog/pcwd-watchdog.txt | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/filesystems/dnotify.txt b/Documentation/filesystems/dnotify.txt
> index 6baf88f46859..15156883d321 100644
> --- a/Documentation/filesystems/dnotify.txt
> +++ b/Documentation/filesystems/dnotify.txt
> @@ -62,7 +62,7 @@ disabled, fcntl(fd, F_NOTIFY, ...) will return -EINVAL.
>
> Example
> -------
> -See Documentation/filesystems/dnotify_test.c for an example.
> +See tools/testing/selftests/filesystems/dnotify_test.c for an example.
>
> NOTE
> ----
> diff --git a/Documentation/watchdog/hpwdt.txt b/Documentation/watchdog/hpwdt.txt
> index 7a9f635d0258..6d866c537127 100644
> --- a/Documentation/watchdog/hpwdt.txt
> +++ b/Documentation/watchdog/hpwdt.txt
> @@ -15,7 +15,7 @@ Last reviewed: 05/20/2016
>
> Watchdog functionality is enabled like any other common watchdog driver. That
> is, an application needs to be started that kicks off the watchdog timer. A
> - basic application exists in the Documentation/watchdog/src directory called
> + basic application exists in tools/testing/selftests/watchdog/ named
> watchdog-test.c. Simply compile the C file and kick it off. If the system
> gets into a bad state and hangs, the HPE ProLiant iLO timer register will
> not be updated in a timely fashion and a hardware system reset (also known as
> diff --git a/Documentation/watchdog/pcwd-watchdog.txt b/Documentation/watchdog/pcwd-watchdog.txt
> index 4f68052395c0..b8e60a441a43 100644
> --- a/Documentation/watchdog/pcwd-watchdog.txt
> +++ b/Documentation/watchdog/pcwd-watchdog.txt
> @@ -25,7 +25,7 @@ Last reviewed: 10/05/2007
>
> If you want to write a program to be compatible with the PC Watchdog
> driver, simply use of modify the watchdog test program:
> - Documentation/watchdog/src/watchdog-test.c
> + tools/testing/selftests/watchdog/watchdog-test.c
>
>
> Other IOCTL functions include:
next prev parent reply other threads:[~2017-10-22 16:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 20:23 [PATCH 0/8] Documentation: fix invalid Documentation refs (2) Tom Saeger
2017-10-12 20:23 ` [PATCH 1/8] Documentation: fix locking rt-mutex doc refs Tom Saeger
2017-10-12 20:23 ` [PATCH 2/8] Documentation: fix ref to sphinx/kerneldoc.py Tom Saeger
2017-10-12 20:23 ` [PATCH 3/8] Documentation: fix ref to workqueue content Tom Saeger
2017-10-13 8:03 ` Jani Nikula
2017-10-12 20:23 ` [PATCH 4/8] Documentation: fix ref to coccinelle content Tom Saeger
2017-10-12 20:23 ` [PATCH 5/8] Documentation: fix ref to trace stm content Tom Saeger
2017-10-12 20:24 ` [PATCH 6/8] Documentation: fix ref to power basic-pm-debugging Tom Saeger
2017-10-12 20:46 ` Rafael J. Wysocki
2017-10-12 20:24 ` [PATCH 7/8] Documentation: fix selftests related file refs Tom Saeger
2017-10-20 16:53 ` Jerry Hoemann
2017-10-22 16:23 ` Guenter Roeck [this message]
2017-10-12 20:24 ` [PATCH 8/8] Documentation: fix ref to gpio.txt Tom Saeger
2017-10-16 12:03 ` Linus Walleij
2017-10-19 18:59 ` [PATCH 0/8] Documentation: fix invalid Documentation refs (2) 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=20171022162346.GA13195@roeck-us.net \
--to=linux@roeck-us.net \
--cc=amir73il@gmail.com \
--cc=corbet@lwn.net \
--cc=jack@suse.cz \
--cc=jimmy.vance@hpe.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=tom.saeger@oracle.com \
--cc=wim@iguana.be \
/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
Powered by JetHome