From: Johan Hovold <johan@kernel.org>
To: Zijun Hu <quic_zijuhu@quicinc.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Johan Hovold <johan+linaro@kernel.org>,
Tony Lindgren <tony@atomide.com>, Zijun Hu <zijun_hu@icloud.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] PM: sleep: wakeirq: Fix a serious logical error in dev_pm_disarm_wake_irq()
Date: Mon, 30 Sep 2024 15:07:13 +0200 [thread overview]
Message-ID: <ZvqigTC7RvngLpme@hovoldconsulting.com> (raw)
In-Reply-To: <20240928-fix_wakeirq-v1-1-25d13a7e13ba@quicinc.com>
On Sat, Sep 28, 2024 at 02:26:27AM -0700, Zijun Hu wrote:
> IT is a serious logical error for dev_pm_disarm_wake_irq() not to disable
> the wake irq enabled by dev_pm_arm_wake_irq()
You need to explain *why* you believe this is an error.
> fixed by simply correcting
> the wrong if condition.
Your commit message is basically just claims "P is wrong, fix P", which
doesn't really explain anything.
Writing good commit messages explaining what the problem is is not just
required because this is a collaborative project where others need to
understand your reasoning, but it also forces you as the author to think
through your changes, which can often prevent broken patches from being
submitted in the first place.
> Signed-off-by: Zijun Hu <quic_zijuhu@quicinc.com>
> ---
> List relevant commits as following:
>
> johan+linaro@kernel.org 2023-07-13
> Commit: 8527beb12087 ("PM: sleep: wakeirq: fix wake irq arming")
>
> tony@atomide.com 2018-02-09
> Commit: 69728051f5bf ("PM / wakeirq: Fix unbalanced IRQ enable for wakeirq")
>
> The former commit fixes the later.
These references are relevant, but you need to include them in your
commit messages (above ---) and explain why.
> ---
> drivers/base/power/wakeirq.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/base/power/wakeirq.c b/drivers/base/power/wakeirq.c
> index 5a5a9e978e85..8b15f9a0e8f9 100644
> --- a/drivers/base/power/wakeirq.c
> +++ b/drivers/base/power/wakeirq.c
> @@ -356,7 +356,7 @@ void dev_pm_disarm_wake_irq(struct wake_irq *wirq)
> disable_irq_wake(wirq->irq);
>
> if (wirq->status & WAKE_IRQ_DEDICATED_ALLOCATED &&
> - !(wirq->status & WAKE_IRQ_DEDICATED_ENABLED))
> + (wirq->status & WAKE_IRQ_DEDICATED_ENABLED))
> disable_irq_nosync(wirq->irq);
I think the current code works as intended.
> }
> }
Johan
next prev parent reply other threads:[~2024-09-30 13:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-28 9:26 [PATCH RFC] PM: sleep: wakeirq: Fix a serious logical error in dev_pm_disarm_wake_irq() Zijun Hu
2024-09-28 10:50 ` Greg Kroah-Hartman
2024-09-28 16:08 ` quic_zijuhu
2024-09-30 13:07 ` Johan Hovold [this message]
2024-10-10 13:24 ` Zijun Hu
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=ZvqigTC7RvngLpme@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=johan+linaro@kernel.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=quic_zijuhu@quicinc.com \
--cc=rafael@kernel.org \
--cc=tony@atomide.com \
--cc=zijun_hu@icloud.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;
as well as URLs for NNTP newsgroup(s).