On Tue, 12 Oct 2021 19:11:29 +0000 "Shankar, Uma" <uma.shan...@intel.com> wrote:
> > -----Original Message----- > > From: Pekka Paalanen <ppaala...@gmail.com> > > Sent: Tuesday, October 12, 2021 5:30 PM > > To: Simon Ser <cont...@emersion.fr> > > Cc: Shankar, Uma <uma.shan...@intel.com>; intel-gfx@lists.freedesktop.org; > > dri- > > de...@lists.freedesktop.org; harry.wentl...@amd.com; > > ville.syrj...@linux.intel.com; brian.star...@arm.com; > > sebast...@sebastianwick.net; shashank.sha...@amd.com > > Subject: Re: [RFC v2 01/22] drm: RFC for Plane Color Hardware Pipeline > > > > On Tue, 12 Oct 2021 10:35:37 +0000 > > Simon Ser <cont...@emersion.fr> wrote: > > > > > On Tuesday, October 12th, 2021 at 12:30, Pekka Paalanen > > <ppaala...@gmail.com> wrote: > > > > > > > is there a practise of landing proposal documents in the kernel? How > > > > does that work, will a kernel tree carry the patch files? > > > > Or should this document be worded like documentation for an accepted > > > > feature, and then the patches either land or don't? > > > > > > Once everyone agrees, the RFC can land. I don't think a kernel tree is > > > necessary. See: > > > > > > https://dri.freedesktop.org/docs/drm/gpu/rfc/index.html > > > > Does this mean the RFC doc patch will land, but the code patches will > > remain in the > > review cycles waiting for userspace proving vehicles? > > Rather than e.g. committed as files that people would need to apply > > themselves? Or > > how does one find the code patches corresponding to RFC docs? > > As I understand, this section was added to finalize the design and debate on > the UAPI, > structures, headers and design etc. Once a general agreement is in place with > all the > stakeholders, we can have ack on design and approach and get it merged. This > hence > serves as an approved reference for the UAPI, accepted and agreed by > community at large. > > Once the code lands, all the documentation will be added to the right driver > sections and > helpers, like it's been done currently. I'm just wondering: someone browses a kernel tree, and discovers this RFC doc in there. They want to see or test the latest (WIP) kernel implementation of it. How will they find the code / patches? Thanks, pq
pgpZjiSLSTD4M.pgp
Description: OpenPGP digital signature
