[RFC v2 01/22] drm: RFC for Plane Color Hardware Pipeline
Pekka Paalanen
ppaalanen at gmail.com
Tue Oct 12 12:00:11 UTC 2021
On Tue, 12 Oct 2021 10:35:37 +0000
Simon Ser <contact at emersion.fr> wrote:
> On Tuesday, October 12th, 2021 at 12:30, Pekka Paalanen <ppaalanen at 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?
Thanks,
pq
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20211012/29d32c92/attachment.sig>
More information about the dri-devel
mailing list