Re: [PATCH 1/2] drm/doc: Allow new UAPI to be used once it's in the driver's -next.

2019-04-24 Thread Dave Airlie
On Thu, 25 Apr 2019 at 05:35, Daniel Vetter wrote: > > On Wed, Apr 24, 2019 at 11:56:16AM -0700, Eric Anholt wrote: > > I was trying to figure out if it was permissible to merge the Mesa > > side of V3D's CSD support yet while it's in drm-misc-next but not > > drm-next, and developers on #dri-deve

Re: [PATCH 1/2] drm/doc: Allow new UAPI to be used once it's in the driver's -next.

2019-04-24 Thread Daniel Vetter
On Wed, Apr 24, 2019 at 11:56:16AM -0700, Eric Anholt wrote: > I was trying to figure out if it was permissible to merge the Mesa > side of V3D's CSD support yet while it's in drm-misc-next but not > drm-next, and developers on #dri-devel IRC had differing opinions of > what the requirement was. P

[PATCH 1/2] drm/doc: Allow new UAPI to be used once it's in the driver's -next.

2019-04-24 Thread Eric Anholt
I was trying to figure out if it was permissible to merge the Mesa side of V3D's CSD support yet while it's in drm-misc-next but not drm-next, and developers on #dri-devel IRC had differing opinions of what the requirement was. Propose a clarification here to see if Dave Airlie agrees. Signed-off