From: patchwork-bot+linux-arm-msm@kernel.org
To: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] watchdog: qcom: Remove incorrect usage of QCOM_WDT_ENABLE_IRQ
Date: Mon, 01 Mar 2021 19:59:44 +0000 [thread overview]
Message-ID: <161462878455.6187.9799239261412669846.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210126150241.10009-1-saiprakash.ranjan@codeaurora.org>
Hello:
This patch was applied to qcom/linux.git (refs/heads/for-next):
On Tue, 26 Jan 2021 20:32:41 +0530 you wrote:
> As per register documentation, QCOM_WDT_ENABLE_IRQ which is BIT(1)
> of watchdog control register is wakeup interrupt enable bit and
> not related to bark interrupt at all, BIT(0) is used for that.
> So remove incorrect usage of this bit when supporting bark irq for
> pre-timeout notification. Currently with this bit set and bark
> interrupt specified, pre-timeout notification and/or watchdog
> reset/bite does not occur.
>
> [...]
Here is the summary with links:
- watchdog: qcom: Remove incorrect usage of QCOM_WDT_ENABLE_IRQ
https://git.kernel.org/qcom/c/a4f3407c4160
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-03-01 20:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 15:02 [PATCH] watchdog: qcom: Remove incorrect usage of QCOM_WDT_ENABLE_IRQ Sai Prakash Ranjan
2021-01-26 15:23 ` Guenter Roeck
2021-01-26 15:23 ` Guenter Roeck
2021-01-26 15:53 ` Sai Prakash Ranjan
2021-01-28 1:33 ` Stephen Boyd
2021-01-28 1:33 ` Stephen Boyd
2021-01-28 11:03 ` Sai Prakash Ranjan
2021-01-28 8:19 ` Jorge Ramirez-Ortiz, Foundries
2021-01-28 8:19 ` Jorge Ramirez-Ortiz, Foundries
2021-01-28 11:08 ` Sai Prakash Ranjan
2021-01-31 17:03 ` Jorge Ramirez-Ortiz, Foundries
2021-03-01 19:59 ` patchwork-bot+linux-arm-msm [this message]
2021-02-01 5:53 Sai Prakash Ranjan
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=161462878455.6187.9799239261412669846.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-arm-msm@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=saiprakash.ranjan@codeaurora.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 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.