mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wang Qing <wangqing@vivo.com>
To: Jonathan Corbet <corbet@lwn.net>, Wang Qing <wangqing@vivo.com>,
	Joe Perches <joe@perches.com>,
	Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Stephen Kitt <steve@sk2.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Kees Cook <keescook@chromium.org>,
	"Guilherme G. Piccoli" <gpiccoli@canonical.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	Andrew Klychkov <andrew.a.klychkov@gmail.com>,
	Rafael Aquini <aquini@redhat.com>,
	Qais Yousef <qais.yousef@arm.com>, Petr Mladek <pmladek@suse.com>,
	Santosh Sivaraj <santosh@fossix.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH V2,RESEND 0/4] kernel/watchdog: Modify the explanation and doc related to watchdog thread
Date: Thu, 29 Apr 2021 14:37:10 +0800	[thread overview]
Message-ID: <1619678239-2289-1-git-send-email-wangqing@vivo.com> (raw)

"watchdog/%u" threads has be replaced by cpu_stop_work. The current 
description is extremely misleading, so we need to modify the 
explanation and documentation related to this.

Wang Qing (4):
  kernel: watchdog: Modify the explanation related to watchdog thread
  doc: watchdog: Delete the explanation about "watchdog/%u".
  doc: watchdog: Modify the explanation related to watchdog thread
  doc: watchdog: Modify the doc related to "watchdog/%u"

 .../admin-guide/kernel-per-CPU-kthreads.rst          | 20 --------------------
 Documentation/admin-guide/lockup-watchdogs.rst       |  4 ++--
 Documentation/admin-guide/sysctl/kernel.rst          | 10 +++++-----
 kernel/watchdog.c                                    | 12 ++++--------
 4 files changed, 11 insertions(+), 35 deletions(-)

-- 
2.7.4


                 reply	other threads:[~2021-04-29  6:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1619678239-2289-1-git-send-email-wangqing@vivo.com \
    --to=wangqing@vivo.com \
    --cc=akpm@linux-foundation.org \
    --cc=andrew.a.klychkov@gmail.com \
    --cc=aquini@redhat.com \
    --cc=corbet@lwn.net \
    --cc=gpiccoli@canonical.com \
    --cc=joe@perches.com \
    --cc=keescook@chromium.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=pmladek@suse.com \
    --cc=qais.yousef@arm.com \
    --cc=rdunlap@infradead.org \
    --cc=santosh@fossix.org \
    --cc=steve@sk2.org \
    /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

all inboxes | Powered by JetHome®