From: Guenter Roeck <linux@roeck-us.net>
To: Tomer Maimon <tmaimon77@gmail.com>
Cc: andrew@codeconstruct.com.au, wim@linux-watchdog.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
openbmc@lists.ozlabs.org, linux-watchdog@vger.kernel.org,
linux-doc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, avifishman70@gmail.com,
tali.perry1@gmail.com, venture@google.com, yuenn@google.com,
benjaminfair@google.com, corbet@lwn.net,
skhan@linuxfoundation.org, joel@jms.id.au
Subject: Re: [PATCH v4 2/3] docs: watchdog: npcm: Add reset status description
Date: Mon, 20 Jul 2026 09:10:27 -0700 [thread overview]
Message-ID: <ebe0fffb-eeb4-4dba-ae8d-7153af6c2fbe@roeck-us.net> (raw)
In-Reply-To: <20260706144828.3517631-3-tmaimon77@gmail.com>
On Mon, Jul 06, 2026 at 05:48:27PM +0300, Tomer Maimon wrote:
> Add documentation describing how the NPCM watchdog driver reports reset
> causes through bootstatus on NPCM750 and NPCM845 systems.
>
> Document the reset flag mapping, the watchdog instance mapping for
> WDIOF_CARDRESET, and the NPCM750/NPCM845 latch handling. Also mention
> sysfs bootstatus reporting when watchdog sysfs support is enabled.
>
> Signed-off-by: Tomer Maimon <tmaimon77@gmail.com>
Applied.
Thanks,
Guenter
next prev parent reply other threads:[~2026-07-20 16:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 14:48 [PATCH v4 0/3] watchdog: npcm: Add reset status detection support Tomer Maimon
2026-07-06 14:48 ` [PATCH v4 1/3] dt-bindings: watchdog: npcm: add GCR syscon property Tomer Maimon
2026-07-06 16:57 ` Conor Dooley
2026-07-20 16:09 ` Guenter Roeck
2026-07-06 14:48 ` [PATCH v4 2/3] docs: watchdog: npcm: Add reset status description Tomer Maimon
2026-07-20 16:10 ` Guenter Roeck [this message]
2026-07-06 14:48 ` [PATCH v4 3/3] watchdog: npcm: add bootstatus support Tomer Maimon
2026-07-20 16:11 ` Guenter Roeck
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=ebe0fffb-eeb4-4dba-ae8d-7153af6c2fbe@roeck-us.net \
--to=linux@roeck-us.net \
--cc=andrew@codeconstruct.com.au \
--cc=avifishman70@gmail.com \
--cc=benjaminfair@google.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=robh@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=tali.perry1@gmail.com \
--cc=tmaimon77@gmail.com \
--cc=venture@google.com \
--cc=wim@linux-watchdog.org \
--cc=yuenn@google.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