From: Raag Jadav <raag.jadav@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Maarten Lankhorst <dev@lankhorst.se>,
intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915/display: Fix intel_lpe_audio_irq_handler for PREEMPT-RT
Date: Thu, 11 Dec 2025 15:05:52 +0100 [thread overview]
Message-ID: <aTrPwDcYsMMJhSPv@black.igk.intel.com> (raw)
In-Reply-To: <e0ba6a112e0150731a23934109e1419d07e526e2@intel.com>
On Thu, Dec 11, 2025 at 10:47:01AM +0200, Jani Nikula wrote:
> On Wed, 10 Dec 2025, Maarten Lankhorst <dev@lankhorst.se> wrote:
> > Hey,
> >
> > Just needs a typo fixed, Matthew Brost also commented that the second I915 here should be PREEMPT-RT instead.
>
> The commit message does not say what is being done here, and why.
>
> "no need for backporting"?
>
> "this is only useful for i915"?
>
> *what* "doesn't compile with PREEMPT-RT enabled"?
>
> Nobody's going to understand what any of this means if a bisect/blame
> lands here a couple of years from now, even if it's an apparently simple
> change.
I've been looking at some of the AMD patches and found the template
to be much useful.
Subject: [WHAT]
Commit message:
[WHY]
[HOW]
Not a hard mandate but worth thinking in this direction?
Raag
> > Den 2025-12-10 kl. 09:56, skrev Jani Nikula:
> >> On Tue, 09 Dec 2025, Maarten Lankhorst <dev@lankhorst.se> wrote:
> >>> No need for backporting, this is only useful for i915,
> >>> and it doesn't compile with I915 enabled.
> >>
> >> Please elaborate. There's just riddles here.
> >>
> >> BR,
> >> Jani.
> >>
> >>>
> >>> Signed-off-by: Maarten Lankhorst <dev@lankhorst.se>
> >>> ---
> >>> drivers/gpu/drm/i915/display/intel_lpe_audio.c | 2 +-
> >>> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>>
> >>> diff --git a/drivers/gpu/drm/i915/display/intel_lpe_audio.c b/drivers/gpu/drm/i915/display/intel_lpe_audio.c
> >>> index 5b41abe1c64d5..172c0062237eb 100644
> >>> --- a/drivers/gpu/drm/i915/display/intel_lpe_audio.c
> >>> +++ b/drivers/gpu/drm/i915/display/intel_lpe_audio.c
> >>> @@ -262,7 +262,7 @@ void intel_lpe_audio_irq_handler(struct intel_display *display)
> >>> if (!HAS_LPE_AUDIO(display))
> >>> return;
> >>>
> >>> - ret = generic_handle_irq(display->audio.lpe.irq);
> >>> + ret = generic_handle_irq_safe(display->audio.lpe.irq);
> >>> if (ret)
> >>> drm_err_ratelimited(display->drm,
> >>> "error handling LPE audio irq: %d\n", ret);
> >>
> >
>
> --
> Jani Nikula, Intel
next prev parent reply other threads:[~2025-12-11 14:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-09 15:13 [PATCH 1/2] drm/xe: Use generic_handle_irq_safe inside heci gsc irq handler Maarten Lankhorst
2025-12-09 15:13 ` [PATCH 2/2] drm/i915/display: Fix intel_lpe_audio_irq_handler for PREEMPT-RT Maarten Lankhorst
2025-12-09 22:42 ` Matthew Brost
2025-12-10 8:56 ` Jani Nikula
2025-12-10 17:00 ` Maarten Lankhorst
2025-12-11 8:47 ` Jani Nikula
2025-12-11 9:48 ` Maarten Lankhorst
2025-12-11 14:05 ` Raag Jadav [this message]
2025-12-11 14:34 ` Jani Nikula
2025-12-09 18:45 ` ✓ CI.KUnit: success for series starting with [1/2] drm/xe: Use generic_handle_irq_safe inside heci gsc irq handler Patchwork
2025-12-09 21:07 ` ✓ Xe.CI.BAT: " Patchwork
2025-12-09 22:39 ` [PATCH 1/2] " Matthew Brost
2025-12-10 0:34 ` ✗ Xe.CI.Full: failure for series starting with [1/2] " Patchwork
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=aTrPwDcYsMMJhSPv@black.igk.intel.com \
--to=raag.jadav@intel.com \
--cc=dev@lankhorst.se \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.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