From: Simon Richter <Simon.Richter@hogyros.de>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3 1/1] drm/i915: handle failure from vga_get_uninterruptible()
Date: Tue, 10 Mar 2026 23:45:53 +0900 [thread overview]
Message-ID: <45f30d71-2afc-40fb-ba5d-ffd0bb7e7ee0@hogyros.de> (raw)
In-Reply-To: <aa_8GhVURTdKWRVl@intel.com>
Hi,
On 3/10/26 8:10 PM, Ville Syrjälä wrote:
> Do you need to take this in via some other tree, or should I just push
> it to drm-intel-next?
This is independent from the PCI changes (and I didn't Cc linux-pci on
this one), so via drm-intel-next would be best, thanks!
I've also prepared a backported version for 5.3 to 6.19 kernels[1].
Simon
[1] https://patchwork.freedesktop.org/patch/709684/?series=161721&rev=4
next prev parent reply other threads:[~2026-03-10 14:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 16:51 [PATCH 0/1] Avoid oops on illegal VGA register access Simon Richter
2026-02-17 16:51 ` [PATCH 1/1] drm/i915: handle failure from vga_get Simon Richter
2026-02-18 13:10 ` [PATCH v2 " Simon Richter
2026-03-06 15:13 ` [PATCH v3 1/1] drm/i915: handle failure from vga_get_uninterruptible() Simon Richter
2026-03-10 11:10 ` Ville Syrjälä
2026-03-10 14:45 ` Simon Richter [this message]
2026-03-10 15:11 ` Ville Syrjälä
2026-02-26 10:44 ` [PATCH 1/1] drm/i915: handle failure from vga_get Jani Nikula
2026-02-17 17:03 ` ✗ CI.checkpatch: warning for Avoid oops on illegal VGA register access Patchwork
2026-02-17 17:04 ` ✓ CI.KUnit: success " Patchwork
2026-02-17 17:42 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-17 20:50 ` ✓ Xe.CI.FULL: " Patchwork
2026-02-18 17:11 ` ✓ CI.KUnit: success for Avoid oops on illegal VGA register access (rev2) Patchwork
2026-02-18 18:04 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-18 19:47 ` ✓ Xe.CI.FULL: " 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=45f30d71-2afc-40fb-ba5d-ffd0bb7e7ee0@hogyros.de \
--to=simon.richter@hogyros.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=ville.syrjala@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