From: Andrew Morton <akpm@linux-foundation.org>
To: Petr Mladek <pmladek@suse.com>
Cc: Wang Qing <wangqing@vivo.com>, Jonathan Corbet <corbet@lwn.net>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Joe Perches <joe@perches.com>, Stephen Kitt <steve@sk2.org>,
Kees Cook <keescook@chromium.org>,
Randy Dunlap <rdunlap@infradead.org>,
"Guilherme G. Piccoli" <gpiccoli@canonical.com>,
Qais Yousef <qais.yousef@arm.com>,
Santosh Sivaraj <santosh@fossix.org>,
Vlastimil Babka <vbabka@suse.cz>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2,RESEND 1/4] kernel: watchdog: Modify the explanation related to watchdog thread
Date: Sun, 9 May 2021 16:29:17 -0700 [thread overview]
Message-ID: <20210509162917.3a50fef3858f7708a84d1a91@linux-foundation.org> (raw)
In-Reply-To: <YIp8e6ftzUdgX4Yv@alley>
On Thu, 29 Apr 2021 11:29:31 +0200 Petr Mladek <pmladek@suse.com> wrote:
> On Thu 2021-04-29 17:04:25, Wang Qing wrote:
> > The watchdog thread has been replaced by cpu_stop_work, modify the
> > explanation related.
> >
> > Signed-off-by: Wang Qing <wangqing@vivo.com>
>
> You should have added my Reviewed-by when resending the patchset.
> Anyway, for all four patches:
>
> Reviewed-by: Petr Mladek <pmladek@suse.com>
>
> Andrew, would you take it via -mm tree?
Sure. I dropped "[2/4] doc: watchdog: Delete the explanation about
"watchdog/%u"" because someone already did that.
prev parent reply other threads:[~2021-05-09 23:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 9:04 [PATCH V2,RESEND 1/4] kernel: watchdog: Modify the explanation related to watchdog thread Wang Qing
2021-04-29 9:04 ` [PATCH V2,RESEND 2/4] doc: watchdog: Delete the explanation about "watchdog/%u" Wang Qing
2021-04-29 9:04 ` [PATCH V2,RESEND 3/4] doc: watchdog: Modify the explanation related to watchdog thread Wang Qing
2021-04-29 9:04 ` [PATCH V2,RESEND 4/4] doc: watchdog: Modify the doc related to "watchdog/%u" Wang Qing
2021-04-29 9:29 ` [PATCH V2,RESEND 1/4] kernel: watchdog: Modify the explanation related to watchdog thread Petr Mladek
2021-05-09 23:29 ` Andrew Morton [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=20210509162917.3a50fef3858f7708a84d1a91@linux-foundation.org \
--to=akpm@linux-foundation.org \
--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 \
--cc=vbabka@suse.cz \
--cc=wangqing@vivo.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 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.