From: Jani Nikula <jani.nikula@linux.intel.com>
To: Raag Jadav <raag.jadav@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 16:34:42 +0200 [thread overview]
Message-ID: <23cc04865c6f8aa4c3bf31a0c0c5e088a31084bd@intel.com> (raw)
In-Reply-To: <aTrPwDcYsMMJhSPv@black.igk.intel.com>
On Thu, 11 Dec 2025, Raag Jadav <raag.jadav@intel.com> wrote:
> 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?
Yeah, that's what you're basically supposed to do, but I hate having
those template things stay in the commit messages. They're not
necessary.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-12-11 14:34 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
2025-12-11 14:34 ` Jani Nikula [this message]
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=23cc04865c6f8aa4c3bf31a0c0c5e088a31084bd@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=dev@lankhorst.se \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=raag.jadav@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