From: Jani Nikula <jani.nikula@intel.com>
To: "Kasireddy, Vivek" <vivek.kasireddy@intel.com>,
"Roper, Matthew D" <matthew.d.roper@intel.com>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"De Marchi, Lucas" <lucas.demarchi@intel.com>
Subject: RE: [PATCH] drm/xe/bmg: Fix NULL-ptr deref during probe on SKUs with no display
Date: Wed, 04 Jun 2025 11:21:07 +0300 [thread overview]
Message-ID: <60a9f7937cbbd953db5e6b1dacd8d0f7e6d1e775@intel.com> (raw)
In-Reply-To: <IA0PR11MB7185E199BA1AC3599471432FF86CA@IA0PR11MB7185.namprd11.prod.outlook.com>
On Wed, 04 Jun 2025, "Kasireddy, Vivek" <vivek.kasireddy@intel.com> wrote:
> I guess we need a short-term solution to address this problem, at-least
> for Xe. So, do you prefer the revert option or the minimal, safer Xe fix
> you shared above?
Yeah, let's go with the revert. Would you care to post it, please?
Thanks, and sorry for the trouble.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-06-04 8:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 22:11 [PATCH] drm/xe/bmg: Fix NULL-ptr deref during probe on SKUs with no display Vivek Kasireddy
2025-06-02 22:18 ` ✓ CI.Patch_applied: success for " Patchwork
2025-06-02 22:18 ` ✗ CI.checkpatch: warning " Patchwork
2025-06-02 22:20 ` ✓ CI.KUnit: success " Patchwork
2025-06-02 22:30 ` ✓ CI.Build: " Patchwork
2025-06-02 22:33 ` ✓ CI.Hooks: " Patchwork
2025-06-02 22:34 ` ✓ CI.checksparse: " Patchwork
2025-06-02 22:48 ` [PATCH] " Matt Roper
2025-06-03 4:30 ` Kasireddy, Vivek
2025-06-03 8:19 ` Jani Nikula
2025-06-03 8:39 ` Saarinen, Jani
2025-06-04 5:24 ` Kasireddy, Vivek
2025-06-04 8:21 ` Jani Nikula [this message]
2025-06-05 3:41 ` Kasireddy, Vivek
2025-06-02 22:58 ` ✓ Xe.CI.BAT: success for " Patchwork
2025-06-04 0:05 ` ✗ Xe.CI.Full: failure " 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=60a9f7937cbbd953db5e6b1dacd8d0f7e6d1e775@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=vivek.kasireddy@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