Re: [PATCH v2 4/5] drm/atomic: Make the drm_atomic_state documentation less ambiguous

2023-12-18 Thread Maxime Ripard
Hi, On Fri, Dec 15, 2023 at 04:54:28PM +0200, Pekka Paalanen wrote: > On Thu, 14 Dec 2023 11:09:15 +0100 > Maxime Ripard wrote: > > > The current documentation of drm_atomic_state says that it's the "global > > state object". This is confusing since, while it does contain all the > > objects aff

Re: [PATCH v2 4/5] drm/atomic: Make the drm_atomic_state documentation less ambiguous

2023-12-15 Thread Pekka Paalanen
On Thu, 14 Dec 2023 11:09:15 +0100 Maxime Ripard wrote: > The current documentation of drm_atomic_state says that it's the "global > state object". This is confusing since, while it does contain all the > objects affected by an update and their respective states, if an object > isn't affected by

Re: [PATCH v2 4/5] drm/atomic: Make the drm_atomic_state documentation less ambiguous

2023-12-14 Thread Hamza Mahfooz
On 12/14/23 05:09, Maxime Ripard wrote: The current documentation of drm_atomic_state says that it's the "global state object". This is confusing since, while it does contain all the objects affected by an update and their respective states, if an object isn't affected by this update it won't be

[PATCH v2 4/5] drm/atomic: Make the drm_atomic_state documentation less ambiguous

2023-12-14 Thread Maxime Ripard
The current documentation of drm_atomic_state says that it's the "global state object". This is confusing since, while it does contain all the objects affected by an update and their respective states, if an object isn't affected by this update it won't be part of it. Thus, it's not truly a "globa