On Fri, Jun 27, 2025 at 12:10 PM Javier Martinez Canillas <[email protected]> wrote: > > Laurent Pinchart <[email protected]> writes: > > > On Fri, Jun 27, 2025 at 09:39:37AM -0700, Rob Clark wrote: > >> On Mon, Feb 26, 2024 at 5:43 AM Jacopo Mondi wrote: > >> > > >> > Add FourCC definitions for the 48-bit RGB/BGR formats to the > >> > DRM/KMS uapi. > >> > > >> > The format will be used by the Raspberry Pi PiSP Back End, > >> > supported by a V4L2 driver in kernel space and by libcamera in > >> > userspace, which uses the DRM FourCC identifiers. > >> > > >> > Signed-off-by: Jacopo Mondi <[email protected]> > >> > >> Resurrecting this, as it appears to have not ever landed upstream > > > > What are the rule is for patches that touch core code like this one, can > > they be pushed to drm-misc by anyone with commit access, or do they need > > to be collected by a drm-misc maintainer ? > > > > According to [0] I would say that you could just push it through drm-misc > since there are already a few review-by tags collected. > > [0]: > https://drm.pages.freedesktop.org/maintainer-tools/committer/committer-drm-misc.html#merge-criteria
yeah, should be fine to push to drm-misc since it has r-b's (not to mention no negative comments for a _long_ time) BR, -R
