On Tue, Mar 24, 2026 at 03:36:24AM +0100, Raag Jadav wrote:
> On Mon, Mar 23, 2026 at 03:11:58PM +0100, Christian König wrote:
> > On 3/23/26 15:10, Raag Jadav wrote:
> > > On Tue, Mar 10, 2026 at 08:56:58AM +0100, Raag Jadav wrote:
> > >> On Thu, Mar 05, 2026 at 06:36:46PM +0530, Raag Jadav wrote:
> > >>> Currently 'none' recovery method for wedged event expects no explicit
> > >>> recovery from userspace consumer but it expects driver to have reset
> > >>> the device, which may not always be the case. Update documentation and
> > >>> log to reflect this expectation.
> > >>
> > >> Anything I can do to move this forward?
> > 
> > Invent some tech to clone certain people so that we have more reviewers.
> 
> If this allows my clones to also review my patches, I fully support this :)
> 
> > > Ping.
> > 
> > I will take a look now.
> 
> Thank you, I think it's safe to land through drm-misc (if anyone has access).

Acked-by: Rodrigo Vivi <[email protected]>

But it is not applying cleanly on drm-misc-next.

drm-misc maintainers, could you please do a backmerge of drm-next?

Or ack these patches to go through drm-xe-next

> 
> Raag
> 
> > >>> v2: Rephrase documentation (Rodrigo)
> > >>>
> > >>> Raag Jadav (3):
> > >>>   drm/doc: Update documentation for 'none' recovery method
> > >>>   drm: Update log for 'none' recovery method
> > >>>   drm/xe: Send 'none' recovery method for
> > >>>     XE_WEDGED_MODE_UPON_ANY_HANG_NO_RESET
> > >>>
> > >>>  Documentation/gpu/drm-uapi.rst | 14 +++++++-------
> > >>>  drivers/gpu/drm/drm_drv.c      |  2 +-
> > >>>  drivers/gpu/drm/xe/xe_device.c |  9 ++++++++-
> > >>>  3 files changed, 16 insertions(+), 9 deletions(-)
> > >>>
> > >>> -- 
> > >>> 2.43.0
> > >>>
> > 

Reply via email to