All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Simon Richter <Simon.Richter@hogyros.de>
Cc: intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	stable@vger.kernel.org
Subject: Re: [PATCH 1/2] drm/xe: allow request_irq on GSC interrupt
Date: Tue, 17 Mar 2026 15:52:38 +0100	[thread overview]
Message-ID: <2026031723-ridden-prevent-f005@gregkh> (raw)
In-Reply-To: <20260317134741.3420-2-Simon.Richter@hogyros.de>

On Tue, Mar 17, 2026 at 10:47:17PM +0900, Simon Richter wrote:
> The default flags for freshly allocated interrupts are platform dependent,
> and apparently powerpc and arm set IRQ_NOREQUEST by default.
> 
> The normal path is to clear this flag from irq_domain_associate_locked(),
> which wraps the irq domain's "map" function, but the xe driver does not
> define an irq domain and instead allocates the irq descriptor directly, so
> the flags need to be set up manually as well.
> 
> Closes: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/6468
> Fixes: 87a4c85d3a3ed579c86fd2612715ccb94c4001ff

Didn't checkpatch complain about this?  Please use the documented format
for this.

thanks,

greg k-h

  reply	other threads:[~2026-03-17 14:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17 13:47 [PATCH 0/2] MEI interrupt fixes Simon Richter
2026-03-17 13:47 ` [PATCH 1/2] drm/xe: allow request_irq on GSC interrupt Simon Richter
2026-03-17 14:52   ` Greg KH [this message]
2026-03-17 13:47 ` [PATCH 2/2] drm/xe: Use same NUMA node for MEI interrupt Simon Richter
2026-03-17 13:52 ` ✗ CI.checkpatch: warning for MEI interrupt fixes Patchwork
2026-03-17 13:54 ` ✓ CI.KUnit: success " Patchwork
2026-03-17 14:41 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-03-18 23:42 ` ✗ Xe.CI.FULL: " Patchwork
     [not found] <20260317134351.3350-1-Simon.Richter@hogyros.de>
2026-03-17 13:43 ` [PATCH 1/2] drm/xe: allow request_irq on GSC interrupt Simon Richter

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=2026031723-ridden-prevent-f005@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=Simon.Richter@hogyros.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=stable@vger.kernel.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.