From: Raag Jadav <raag.jadav@intel.com>
To: airlied@gmail.com, simona@ffwll.ch, lucas.demarchi@intel.com,
rodrigo.vivi@intel.com, jani.nikula@linux.intel.com,
christian.koenig@amd.com, alexander.deucher@amd.com,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de
Cc: intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, himal.prasad.ghimiray@intel.com,
aravind.iddamsetty@linux.intel.com, anshuman.gupta@intel.com,
andriy.shevchenko@linux.intel.com, lina@asahilina.net,
michal.wajdeczko@intel.com, andrealmeid@igalia.com,
amd-gfx@lists.freedesktop.org, kernel-dev@igalia.com,
xaver.hugl@kde.org, pekka.paalanen@haloniitty.fi
Subject: Re: [PATCH v12 0/5] Introduce DRM device wedged event
Date: Wed, 12 Feb 2025 08:57:10 +0200 [thread overview]
Message-ID: <Z6xGRhC7qrtk7y9t@black.fi.intel.com> (raw)
In-Reply-To: <20250204070528.1919158-1-raag.jadav@intel.com>
On Tue, Feb 04, 2025 at 12:35:23PM +0530, Raag Jadav wrote:
> This series introduces device wedged event in DRM subsystem and uses it
> in xe, i915 and amdgpu drivers. Detailed description in commit message.
>
> This was earlier attempted as xe specific uevent in v1 and v2 on [1].
> Similar work by André Almeida on [2].
> Wedged event support for amdgpu by André Almeida on [3].
> Consumer implementation by Xaver Hugl on [4].
>
> [1] https://patchwork.freedesktop.org/series/136909/
> [2] https://lore.kernel.org/dri-devel/20221125175203.52481-1-andrealmeid@igalia.com/
> [3] https://lore.kernel.org/dri-devel/20241216162104.58241-1-andrealmeid@igalia.com/
> [4] https://invent.kde.org/plasma/kwin/-/merge_requests/7027
Bump. Anything I can do to move this forward?
Raag
next prev parent reply other threads:[~2025-02-12 6:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 7:05 [PATCH v12 0/5] Introduce DRM device wedged event Raag Jadav
2025-02-04 7:05 ` [PATCH v12 1/5] drm: Introduce " Raag Jadav
2025-02-04 15:50 ` Christian König
2025-02-04 7:05 ` [PATCH v12 2/5] drm/doc: Document " Raag Jadav
2025-02-04 7:05 ` [PATCH v12 3/5] drm/xe: Use " Raag Jadav
2025-02-04 17:23 ` Rodrigo Vivi
2025-02-04 7:05 ` [PATCH v12 4/5] drm/i915: " Raag Jadav
2025-02-04 17:24 ` Rodrigo Vivi
2025-02-04 17:40 ` Tvrtko Ursulin
2025-02-04 7:05 ` [PATCH v12 5/5] drm/amdgpu: " Raag Jadav
2025-02-04 7:53 ` ✗ Fi.CI.CHECKPATCH: warning for Introduce DRM device wedged event (rev10) Patchwork
2025-02-04 7:53 ` ✗ Fi.CI.SPARSE: " Patchwork
2025-02-04 8:11 ` ✗ i915.CI.BAT: failure " Patchwork
2025-02-12 6:57 ` Raag Jadav [this message]
2025-02-12 18:25 ` [PATCH v12 0/5] Introduce DRM device wedged event Rodrigo Vivi
2025-02-13 17:16 ` Rodrigo Vivi
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=Z6xGRhC7qrtk7y9t@black.fi.intel.com \
--to=raag.jadav@intel.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=andrealmeid@igalia.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=anshuman.gupta@intel.com \
--cc=aravind.iddamsetty@linux.intel.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=kernel-dev@igalia.com \
--cc=lina@asahilina.net \
--cc=lucas.demarchi@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=michal.wajdeczko@intel.com \
--cc=mripard@kernel.org \
--cc=pekka.paalanen@haloniitty.fi \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=xaver.hugl@kde.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox