From: Prasanna Kumar T S M <ptsm@linux.microsoft.com>
To: Jay Buddhabhatti <jbuddhab@amd.com>
Cc: gregkh@linuxfoundation.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, michal.simek@amd.com,
srivatsa@csail.mit.edu, ssengar@linux.microsoft.com,
tgopinath@linux.microsoft.com
Subject: Re: [PATCH 2/2] soc: xilinx: Fix event manager CPU hotplug state cleanup
Date: Tue, 3 Nov 2026 20:48:55 +0530 [thread overview]
Message-ID: <192a8868-d73a-4f05-9207-b8cea8eaa7fc@linux.microsoft.com> (raw)
In-Reply-To: <8986493a-cc47-4ad2-a142-764d4069c146@amd.com>
Hi Jay,
On 03-11-2026 17:56, Jay Buddhabhatti wrote:
> Hi Prasanna,
>
> On Mon, Nov 02, 2026 at 10:35:15PM -0800, Prasanna Kumar T S M wrote:
> > On driver removal, the event manager removes the CPUHP_AP_ONLINE_DYN
> > CPU hotplug state instead of the its actual state. This can leave the
> > event manager callbacks dangling. Use the actual CPU hotplug state
> > during driver removal.
> >
> > Hotplug registration failures are also ignored, allowing probe to
> > succeed without the callbacks needed to enable event interrupts on
> > CPUs brought online later.
> >
> > Fixes: c7fdb2404f66 ("drivers: soc: xilinx: add xilinx event
> management driver")
> > Signed-off-by: Prasanna Kumar T S M ptsm@linux.microsoft.com
>
> This looks good to me.
>
> A couple of small nits:
>
> - "instead of the its actual state" -> "instead of its actual state"
Thanks for catching this.
> - Minor alignment on the cpuhp_setup_state() continuation lines;
> checkpatch --strict complains.
> CHECK: Alignment should match open parenthesis
> #49: FILE: drivers/soc/xilinx/xlnx_event_manager.c:663:
> + hp_state = cpuhp_setup_state(CPUHP_AP_ONLINE_DYN,
> + "soc/event:starting", xlnx_event_cpuhp_start,
>
> total: 0 errors, 0 warnings, 1 checks, 44 lines checked
I missed this.
I think the issues are minor. Is it possible to fix this while merging
the patch?
>
> Worth Cc: stable@vger.kernel.org as well, given the Fixes tag.
Do I need to send v2 to address this?
>
> Reviewed-by: Jay Buddhabhatti <jay.buddhabhatti@amd.com>
>
> Thanks,
> Jay
Thanks,
Prasanna Kumar
next prev parent reply other threads:[~2026-11-03 15:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 6:20 [PATCH 1/2] mailbox: zynqmp-ipi: Fix " Prasanna Kumar T S M
2026-11-03 6:35 ` [PATCH 2/2] soc: xilinx: Fix event manager " Prasanna Kumar T S M
2026-11-03 12:26 ` Jay Buddhabhatti
2026-11-03 15:18 ` Prasanna Kumar T S M [this message]
2026-11-03 16:05 ` [PATCH 1/2] mailbox: zynqmp-ipi: Fix " kernel test robot
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=192a8868-d73a-4f05-9207-b8cea8eaa7fc@linux.microsoft.com \
--to=ptsm@linux.microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=jbuddhab@amd.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=srivatsa@csail.mit.edu \
--cc=ssengar@linux.microsoft.com \
--cc=tgopinath@linux.microsoft.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
all inboxes | Powered by JetHome®