[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Zfmw5qjlQmiWRDIV@phenom.ffwll.local>
Date: Tue, 19 Mar 2024 16:36:06 +0100
From: Daniel Vetter <daniel@...ll.ch>
To: Maxime Ripard <mripard@...nel.org>
Cc: Sebastian Wick <sebastian.wick@...hat.com>,
David Airlie <airlied@...il.com>, Daniel Vetter <daniel@...ll.ch>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Thomas Zimmermann <tzimmermann@...e.de>,
Jonathan Corbet <corbet@....net>, dri-devel@...ts.freedesktop.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] drm: Document requirements for driver-specific KMS
props in new drivers
On Thu, Mar 14, 2024 at 11:20:09AM +0100, Maxime Ripard wrote:
> On Mon, Mar 11, 2024 at 04:58:58PM +0100, Sebastian Wick wrote:
> > When extending support for a driver-specific KMS property to additional
> > drivers, we should apply all the requirements for new properties and
> > make sure the semantics are the same and documented.
> >
> > v2: devs of the driver which introduced property shall help and ack
> >
> > Signed-off-by: Sebastian Wick <sebastian.wick@...hat.com>
>
> Acked-by: Maxime Ripard <mripard@...nel.org>
>
> We probably want to have Dave or Sima ack on that one too
Yeah that's a good idea and defacto how we handled this - additional users
of anything (whether library or uapi or whatever) get to clean up an
existing mess if it's too bad. But for uapi it's good to be really
explicit and document that.
Acked-by: Daniel Vetter <daniel.vetter@...ll.ch>
Cheers, Sima
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
Powered by blists - more mailing lists