public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tzung-Bi Shih <tzungbi@kernel.org>
To: Lukasz Majczak <lma@chromium.org>
Cc: Gwendal Grignou <gwendal@chromium.org>,
	Radoslaw Biernacki <biernacki@google.com>,
	Wim Van Sebroeck <wim@linux-watchdog.org>,
	Lee Jones <lee@kernel.org>, Benson Leung <bleung@chromium.org>,
	Guenter Roeck <groeck@chromium.org>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org,
	chrome-platform@lists.linux.dev
Subject: Re: [PATCH v4 1/3] platform/chrome: Update binary interface for EC-based watchdog
Date: Mon, 29 Jan 2024 10:42:41 +0800	[thread overview]
Message-ID: <ZbcQoY7q1nuiv6Y8@google.com> (raw)
In-Reply-To: <20240126095721.782782-2-lma@chromium.org>

On Fri, Jan 26, 2024 at 09:57:19AM +0000, Lukasz Majczak wrote:
> Update structures and defines related to EC_CMD_HANG_DETECT
> to allow usage of new EC-based watchdog.
> 
> Signed-off-by: Lukasz Majczak <lma@chromium.org>

If EC_HANG_DETECT_MAX_TIMEOUT has been defined in [1] (which isn't yet):
Acked-by: Tzung-Bi Shih <tzungbi@kernel.org>

[1] https://chromium.googlesource.com/chromiumos/platform/ec/+/refs/heads/main/include/ec_commands.h#4749

  parent reply	other threads:[~2024-01-29  2:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-26  9:57 [PATCH v4 0/3] Introduce EC-based watchdog Lukasz Majczak
2024-01-26  9:57 ` [PATCH v4 1/3] platform/chrome: Update binary interface for " Lukasz Majczak
2024-01-27 16:21   ` Guenter Roeck
2024-01-29  2:42   ` Tzung-Bi Shih [this message]
2024-01-26  9:57 ` [PATCH v4 2/3] watchdog: Add ChromeOS EC-based watchdog driver Lukasz Majczak
2024-01-27 16:20   ` Guenter Roeck
2024-02-01 13:06 ` [GIT PULL] Immutable branch between MFD, CROS and Watchdog due for the v6.9 merge window Lee Jones
2024-02-02 12:47   ` Łukasz Majczak
2024-02-02 12:50     ` Lee Jones
2024-03-25  1:54 ` [PATCH v4 0/3] Introduce EC-based watchdog patchwork-bot+chrome-platform
2024-03-25  2:13 ` patchwork-bot+chrome-platform

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=ZbcQoY7q1nuiv6Y8@google.com \
    --to=tzungbi@kernel.org \
    --cc=biernacki@google.com \
    --cc=bleung@chromium.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=groeck@chromium.org \
    --cc=gwendal@chromium.org \
    --cc=krzk@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=lma@chromium.org \
    --cc=wim@linux-watchdog.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