From: Raag Jadav <raag.jadav@intel.com>
To: Riana Tauro <riana.tauro@intel.com>
Cc: intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
anshuman.gupta@intel.com, rodrigo.vivi@intel.com,
lucas.demarchi@intel.com, aravind.iddamsetty@linux.intel.com,
umesh.nerlige.ramappa@intel.com, frank.scarbrough@intel.com,
sk.anirban@intel.com, simona.vetter@ffwll.ch,
"André Almeida" <andrealmeid@igalia.com>,
"Christian König" <christian.koenig@amd.com>,
"David Airlie" <airlied@gmail.com>
Subject: Re: [PATCH v6 1/9] drm: Add a vendor-specific recovery method to drm device wedged uevent
Date: Fri, 25 Jul 2025 08:22:58 +0300 [thread overview]
Message-ID: <aIMUskx87yAC8y_R@black.fi.intel.com> (raw)
In-Reply-To: <20250724143440.232862-2-riana.tauro@intel.com>
On Thu, Jul 24, 2025 at 08:04:30PM +0530, Riana Tauro wrote:
> This patch addresses the need for a recovery method (firmware flash
> on Firmware errors) introduced in the later patches of Xe KMD.
Documentation/process/submitting-patches.rst +94
Although the guideline is to describe your changes in imperative mood,
e.g. "make xyzzy do frotz" instead of "[This patch] makes xyzzy do frotz",
I have come across some of our (undocumented) conventions that don't adhere
to upstream ones and I'm not sure if this is one of them.
So upto you.
Raag
next prev parent reply other threads:[~2025-07-25 5:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 14:34 [PATCH v6 0/9] Handle Firmware reported Hardware Errors Riana Tauro
2025-07-24 14:34 ` [PATCH v6 1/9] drm: Add a vendor-specific recovery method to drm device wedged uevent Riana Tauro
2025-07-24 16:18 ` Rodrigo Vivi
2025-07-25 5:22 ` Riana Tauro
2025-07-25 5:22 ` Raag Jadav [this message]
2025-07-24 14:34 ` [PATCH v6 2/9] drm/xe: Set GT as wedged before sending " Riana Tauro
2025-07-24 14:34 ` [PATCH v6 3/9] drm/xe: Add a helper function to set recovery method Riana Tauro
2025-07-25 5:34 ` Raag Jadav
2025-07-24 14:34 ` [PATCH v6 4/9] drm/xe/xe_survivability: Refactor survivability mode Riana Tauro
2025-07-25 5:42 ` Raag Jadav
2025-07-24 14:34 ` [PATCH v6 5/9] drm/xe/xe_survivability: Add support for Runtime " Riana Tauro
2025-07-25 5:44 ` Raag Jadav
2025-07-24 14:34 ` [PATCH v6 6/9] drm/xe/doc: Document device wedged and runtime survivability Riana Tauro
2025-07-24 16:20 ` Rodrigo Vivi
2025-07-25 5:50 ` Raag Jadav
2025-07-24 14:34 ` [PATCH v6 7/9] drm/xe: Add support to handle hardware errors Riana Tauro
2025-07-24 14:34 ` [PATCH v6 8/9] drm/xe/xe_hw_error: Handle CSC Firmware reported Hardware errors Riana Tauro
2025-07-24 14:34 ` [PATCH v6 9/9] drm/xe/xe_hw_error: Add fault injection to trigger csc error handler Riana Tauro
2025-07-25 10:33 ` Raag Jadav
2025-07-24 14:39 ` ✗ CI.checkpatch: warning for Handle Firmware reported Hardware Errors (rev6) Patchwork
2025-07-24 14:40 ` ✓ CI.KUnit: success " Patchwork
2025-07-24 14:55 ` ✗ CI.checksparse: warning " Patchwork
2025-07-24 15:20 ` ✓ Xe.CI.BAT: success " Patchwork
2025-07-24 17:36 ` ✗ 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=aIMUskx87yAC8y_R@black.fi.intel.com \
--to=raag.jadav@intel.com \
--cc=airlied@gmail.com \
--cc=andrealmeid@igalia.com \
--cc=anshuman.gupta@intel.com \
--cc=aravind.iddamsetty@linux.intel.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=frank.scarbrough@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=riana.tauro@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=simona.vetter@ffwll.ch \
--cc=sk.anirban@intel.com \
--cc=umesh.nerlige.ramappa@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