All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-arm-msm@kernel.org
To: Robert Marko <robert.marko@sartura.hr>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v4] watchdog: qcom_wdt: set WDOG_HW_RUNNING bit when appropriate
Date: Tue, 29 Dec 2020 20:15:35 +0000	[thread overview]
Message-ID: <160927293512.13751.16976456809248414774.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201031121115.542752-1-robert.marko@sartura.hr>

Hello:

This patch was applied to qcom/linux.git (refs/heads/for-next):

On Sat, 31 Oct 2020 13:11:15 +0100 you wrote:
> If the watchdog hardware is enabled/running during boot, e.g.
> due to a boot loader configuring it, we must tell the
> watchdog framework about this fact so that it can ping the
> watchdog until userspace opens the device and takes over
> control.
> 
> Do so using the WDOG_HW_RUNNING flag that exists for exactly
> that use-case.
> 
> [...]

Here is the summary with links:
  - [v4] watchdog: qcom_wdt: set WDOG_HW_RUNNING bit when appropriate
    https://git.kernel.org/qcom/c/8650d0f9e933

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2020-12-29 20:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-31 12:11 [PATCH v4] watchdog: qcom_wdt: set WDOG_HW_RUNNING bit when appropriate Robert Marko
2020-10-31 14:08 ` Guenter Roeck
2020-11-02  3:58   ` Kathiravan T
2020-11-02  5:03     ` Guenter Roeck
2020-11-02  5:19       ` Kathiravan T
2020-11-30 18:27         ` Robert Marko
2020-11-30 23:56           ` Guenter Roeck
2020-11-30 23:23 ` Bjorn Andersson
2020-12-29 20:15 ` patchwork-bot+linux-arm-msm [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=160927293512.13751.16976456809248414774.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-arm-msm@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=robert.marko@sartura.hr \
    /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.