From: Markus Elfring <Markus.Elfring@web.de>
To: Manush Prajwal <manushprajwal555@gmail.com>,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org,
Angelo Gioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Jassi Brar <jassisinghbrar@gmail.com>,
Matthias Brugger <matthias.bgg@gmail.com>
Subject: Re: [PATCH v4] mailbox: mtk-cmdq: fix runtime PM usage counter leak in cmdq_mbox_flush()
Date: Tue, 25 Aug 2026 20:27:07 +0200 [thread overview]
Message-ID: <8ddf9e4e-971f-4a82-8686-10d9783d4798@web.de> (raw)
In-Reply-To: <6a8dd21e.b12cec6a.f9ff0.b637@mx.google.com>
…
> ---
> v4:
…
> - No functional change from v3. Still no Fixes tag: I don't have a
> git history for this file available in my current environment to
How can this happen?
Are you still looking for more convenient user interfaces?
See also:
* https://git-scm.com/docs/git-blame
* https://www.geeksforgeeks.org/git/how-to-use-git-blame/#an-alternate-option-to-the-command-line-gui-based
* https://stackoverflow.com/questions/31203001/what-does-git-blame-do
> identify the commit that introduced this exit path with confidence,
I assume that corresponding patching experiences can grow.
> and would rather leave the tag off than guess a SHA. Still happy to
> add it in a v5 if Markus or anyone else on Cc can point at the right
> commit.
It would be nice if further advice would be added accordingly.
…
> drivers/mailbox/mtk-cmdq-mailbox.c | 15 +++++++--------…
Regards,
Markus
prev parent reply other threads:[~2026-08-25 18:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 17:34 [PATCH v4] mailbox: mtk-cmdq: fix runtime PM usage counter leak in cmdq_mbox_flush() Manush Prajwal
2026-08-25 18:27 ` Markus Elfring [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=8ddf9e4e-971f-4a82-8686-10d9783d4798@web.de \
--to=markus.elfring@web.de \
--cc=angelogioacchino.delregno@collabora.com \
--cc=jassisinghbrar@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=manushprajwal555@gmail.com \
--cc=matthias.bgg@gmail.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