From: Thomas Gleixner <tglx@kernel.org>
To: Mayank Rungta <mrungta@google.com>
Cc: Doug Anderson <dianders@chromium.org>,
Guenter Roeck <linux@roeck-us.net>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
"Kirill A. Shutemov" <kas@kernel.org>
Subject: Re: [PATCH 2/3] genirq: Export NMI APIs
Date: Tue, 25 Aug 2026 22:01:40 +0200 [thread overview]
Message-ID: <87cxv6geaj.ffs@fw13> (raw)
In-Reply-To: <CABz7rdCKHcXx6U5qo83HaiR_b17CsoQoVVEiZ=03c+h2FUFHpA@mail.gmail.com>
On Mon, Aug 24 2026 at 17:00, Mayank Rungta wrote:
> On Fri, Aug 7, 2026 at 9:00 AM Thomas Gleixner <tglx@kernel.org> wrote:
>> Sorry, I did not pay attention as I was AFK and busy with bugs. I'll
>> have a look once the dust settles on my side (hopefully soonish).
>>
>
> Hi Thomas,
>
> Friendly ping on this thread!
>
> I completely understand maintainer schedules are very busy. If you
> haven't had a chance to look at this by the end of the week, I'm happy
> to take a stab at implementing the NMI teardown synchronization in v2
> myself for your review.
>
> Please let me know if you have any thoughts or guidance on the approach.
I'm stuck in regressions, security fixes and I try to maintain some
private life aside of that. I surely have opinions, but I probably won't
come around to write them down before next week. Feel free to do a v2
and I'll go and look at that.
Thanks,
tglx
next prev parent reply other threads:[~2026-08-25 20:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 21:32 [PATCH 0/3] watchdog: qcom: Support NMI pretimeout warnings Mayank Rungta via B4 Relay
2026-07-30 21:32 ` Mayank Rungta
2026-07-30 21:32 ` [PATCH 1/3] watchdog: pretimeout: Protect governor access with RCU for NMI safety Mayank Rungta via B4 Relay
2026-07-30 21:32 ` Mayank Rungta
2026-07-30 21:46 ` Doug Anderson
2026-08-07 5:34 ` Guenter Roeck
2026-07-30 21:32 ` [PATCH 2/3] genirq: Export NMI APIs Mayank Rungta via B4 Relay
2026-07-30 21:32 ` Mayank Rungta
2026-07-30 21:47 ` sashiko-bot
2026-07-30 21:49 ` Doug Anderson
2026-07-30 22:55 ` Guenter Roeck
2026-07-31 23:18 ` Doug Anderson
2026-08-07 16:00 ` Thomas Gleixner
2026-08-25 0:00 ` Mayank Rungta
2026-08-25 20:01 ` Thomas Gleixner [this message]
2026-07-30 21:32 ` [PATCH 3/3] watchdog: qcom: Register pretimeout interrupt as NMI Mayank Rungta via B4 Relay
2026-07-30 21:32 ` Mayank Rungta
2026-07-30 21:44 ` sashiko-bot
2026-07-30 21:52 ` Doug Anderson
2026-07-31 11:56 ` Konrad Dybcio
2026-07-31 14:12 ` Guenter Roeck
2026-07-31 23:54 ` Mayank Rungta
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=87cxv6geaj.ffs@fw13 \
--to=tglx@kernel.org \
--cc=dianders@chromium.org \
--cc=kas@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mrungta@google.com \
--cc=wim@linux-watchdog.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.