From: "lihuisong (C)" <lihuisong@huawei.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: <linux-acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<jassisinghbrar@gmail.com>, <liuyonglong@huawei.com>
Subject: Re: [PATCH] mailbox: pcc: Fix can't clear level interrupt of type3 in cornor case
Date: Mon, 3 Mar 2025 14:07:05 +0800 [thread overview]
Message-ID: <ab9f011f-970a-73b1-37cb-158654d0e1db@huawei.com> (raw)
In-Reply-To: <20250302144744.h6ybi4sstxduesvh@bogus>
在 2025/3/2 22:47, Sudeep Holla 写道:
> On Sun, Mar 02, 2025 at 03:30:01PM +0800, lihuisong (C) wrote:
>> 在 2025/3/1 0:32, Sudeep Holla 写道:
> [...]
>
>>> This may be correct way of fixing the issue here, but I am questioning the
>>> existence of this flag now. I have some rework on this file. I will pick
>> This flag is for shared interrupt case on type3. please see:
>> 3db174e478cb ("mailbox: pcc: Support shared interrupt for multiple
>> subspaces")
>>
> Yes, I looked at all the history of this patch and I saw I had suggested
> it. So it took a while to recall why it is a must. I was reworking some
> of the recent change added which I couldn't review and got merged. I was
I konw and understand.
> convinced for a short period this flag is not needed but I was wrong.
>
> I will repost the patch with minor updated to the commit message as part
> of my series soon to avoid any conflicts.
>
ok, looking forward to your series.
> .
prev parent reply other threads:[~2025-03-03 6:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 7:23 [PATCH] mailbox: pcc: Fix can't clear level interrupt of type3 in cornor case Huisong Li
2025-02-28 16:32 ` Sudeep Holla
2025-03-02 7:30 ` lihuisong (C)
2025-03-02 14:47 ` Sudeep Holla
2025-03-03 6:07 ` lihuisong (C) [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=ab9f011f-970a-73b1-37cb-158654d0e1db@huawei.com \
--to=lihuisong@huawei.com \
--cc=jassisinghbrar@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuyonglong@huawei.com \
--cc=sudeep.holla@arm.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