[PATCH AUTOSEL 6.13 14/17] drm/nouveau: Do not override forced connector status

2025-03-03 Thread Sasha Levin
From: Thomas Zimmermann [ Upstream commit 01f1d77a2630e774ce33233c4e6723bca3ae9daa ] Keep user-forced connector status even if it cannot be programmed. Same behavior as for the rest of the drivers. Signed-off-by: Thomas Zimmermann Signed-off-by: Lyude Paul Link: https://patchwork.freedesktop

[PATCH AUTOSEL 6.12 14/17] drm/nouveau: Do not override forced connector status

2025-03-03 Thread Sasha Levin
From: Thomas Zimmermann [ Upstream commit 01f1d77a2630e774ce33233c4e6723bca3ae9daa ] Keep user-forced connector status even if it cannot be programmed. Same behavior as for the rest of the drivers. Signed-off-by: Thomas Zimmermann Signed-off-by: Lyude Paul Link: https://patchwork.freedesktop

[PATCH AUTOSEL 6.6 09/11] drm/nouveau: Do not override forced connector status

2025-03-03 Thread Sasha Levin
From: Thomas Zimmermann [ Upstream commit 01f1d77a2630e774ce33233c4e6723bca3ae9daa ] Keep user-forced connector status even if it cannot be programmed. Same behavior as for the rest of the drivers. Signed-off-by: Thomas Zimmermann Signed-off-by: Lyude Paul Link: https://patchwork.freedesktop

[PATCH AUTOSEL 5.15 8/9] drm/nouveau: Do not override forced connector status

2025-03-03 Thread Sasha Levin
From: Thomas Zimmermann [ Upstream commit 01f1d77a2630e774ce33233c4e6723bca3ae9daa ] Keep user-forced connector status even if it cannot be programmed. Same behavior as for the rest of the drivers. Signed-off-by: Thomas Zimmermann Signed-off-by: Lyude Paul Link: https://patchwork.freedesktop

[PATCH AUTOSEL 5.4 3/4] drm/nouveau: Do not override forced connector status

2025-03-03 Thread Sasha Levin
From: Thomas Zimmermann [ Upstream commit 01f1d77a2630e774ce33233c4e6723bca3ae9daa ] Keep user-forced connector status even if it cannot be programmed. Same behavior as for the rest of the drivers. Signed-off-by: Thomas Zimmermann Signed-off-by: Lyude Paul Link: https://patchwork.freedesktop

[PATCH AUTOSEL 5.10 7/8] drm/nouveau: Do not override forced connector status

2025-03-03 Thread Sasha Levin
From: Thomas Zimmermann [ Upstream commit 01f1d77a2630e774ce33233c4e6723bca3ae9daa ] Keep user-forced connector status even if it cannot be programmed. Same behavior as for the rest of the drivers. Signed-off-by: Thomas Zimmermann Signed-off-by: Lyude Paul Link: https://patchwork.freedesktop

[PATCH AUTOSEL 6.1 8/9] drm/nouveau: Do not override forced connector status

2025-03-03 Thread Sasha Levin
From: Thomas Zimmermann [ Upstream commit 01f1d77a2630e774ce33233c4e6723bca3ae9daa ] Keep user-forced connector status even if it cannot be programmed. Same behavior as for the rest of the drivers. Signed-off-by: Thomas Zimmermann Signed-off-by: Lyude Paul Link: https://patchwork.freedesktop

[PATCH RESEND] drm/nouveau: Add a jump label in nouveau_gem_ioctl_pushbuf()

2025-03-03 Thread Markus Elfring
From: Markus Elfring Date: Wed, 5 Apr 2023 18:38:54 +0200 The label “out_prevalid” was used to jump to another pointer check despite of the detail in the implementation of the function “nouveau_gem_ioctl_pushbuf” that it was determined already in one case that the corresponding variable contained

Re: [PATCH RESEND] drm/nouveau: Add a jump label in nouveau_gem_ioctl_pushbuf()

2025-03-03 Thread Lyude Paul
Oh I didn't even notice this, thanks Danilo :) On Mon, 2025-03-03 at 20:41 +0100, Danilo Krummrich wrote: > On Mon, Mar 03, 2025 at 06:49:07PM +0100, Markus Elfring wrote: > > From: Markus Elfring > > Date: Wed, 5 Apr 2023 18:38:54 +0200 > > > > The label “out_prevalid” was used to jump to anoth

Re: [RFC PATCH 0/3] gpu: nova-core: add basic timer subdevice implementation

2025-03-03 Thread Jason Gunthorpe
On Mon, Mar 03, 2025 at 08:36:34PM +0100, Danilo Krummrich wrote: > > > And yes, for *device resources* it is unsound if we do not ensure that the > > > device resource is actually dropped at device unbind. > > > > Why not do a runtime validation then? > > > > It would be easy to have an atomic c

Re: [RFC PATCH 0/3] gpu: nova-core: add basic timer subdevice implementation

2025-03-03 Thread Danilo Krummrich
On Fri, Feb 28, 2025 at 02:55:34PM -0400, Jason Gunthorpe wrote: > On Thu, Feb 27, 2025 at 11:40:53PM +0100, Danilo Krummrich wrote: > > On Thu, Feb 27, 2025 at 06:00:13PM -0400, Jason Gunthorpe wrote: > > > On Thu, Feb 27, 2025 at 01:25:10PM -0800, Boqun Feng wrote: > > > > > > > > Most of the ca

Re: [PATCH RESEND] drm/nouveau: Add a jump label in nouveau_gem_ioctl_pushbuf()

2025-03-03 Thread Lyude Paul
Reviewed-by: Lyude Paul Will push to drm-misc in a moment On Mon, 2025-03-03 at 18:49 +0100, Markus Elfring wrote: > From: Markus Elfring > Date: Wed, 5 Apr 2023 18:38:54 +0200 > > The label “out_prevalid” was used to jump to another pointer check > despite of the detail in the implementation

Re: [PATCH RESEND] drm/nouveau: Add a jump label in nouveau_gem_ioctl_pushbuf()

2025-03-03 Thread Danilo Krummrich
On Mon, Mar 03, 2025 at 06:49:07PM +0100, Markus Elfring wrote: > From: Markus Elfring > Date: Wed, 5 Apr 2023 18:38:54 +0200 > > The label “out_prevalid” was used to jump to another pointer check > despite of the detail in the implementation of the function > “nouveau_gem_ioctl_pushbuf” that it

Re: [PATCH RESEND] drm/nouveau: Add a jump label in nouveau_gem_ioctl_pushbuf()

2025-03-03 Thread Dan Carpenter
On Mon, Mar 03, 2025 at 08:41:06PM +0100, Danilo Krummrich wrote: > On Mon, Mar 03, 2025 at 06:49:07PM +0100, Markus Elfring wrote: > > From: Markus Elfring > > Date: Wed, 5 Apr 2023 18:38:54 +0200 > > > > The label “out_prevalid” was used to jump to another pointer check > > despite of the detai