Re: [PATCH] drm/fourcc: Document open source user waiver

2023-01-05 Thread Daniel Vetter
Thanks for all the acks, added them all and applied the patch. -Daniel On Fri, Dec 02, 2022 at 02:14:03AM +0100, Bas Nieuwenhuizen wrote: > Acked-by: Bas Nieuwenhuizen > > On Thu, Dec 1, 2022 at 8:47 PM Jason Ekstrand wrote: > > > > Acked-by: Jason Ekstrand > > > > On Thu, Dec 1, 2022 at 4:22

Re: [PATCH] drm/fourcc: Document open source user waiver

2022-12-01 Thread Bas Nieuwenhuizen
Acked-by: Bas Nieuwenhuizen On Thu, Dec 1, 2022 at 8:47 PM Jason Ekstrand wrote: > > Acked-by: Jason Ekstrand > > On Thu, Dec 1, 2022 at 4:22 AM Daniel Vetter wrote: >> >> On Thu, 1 Dec 2022 at 11:07, Daniel Vetter wrote: >> > >> > On Wed, Nov 23, 2022 at 08:24:37PM +0100, Daniel Vetter wrote

Re: [PATCH] drm/fourcc: Document open source user waiver

2022-12-01 Thread Jason Ekstrand
Acked-by: Jason Ekstrand On Thu, Dec 1, 2022 at 4:22 AM Daniel Vetter wrote: > On Thu, 1 Dec 2022 at 11:07, Daniel Vetter wrote: > > > > On Wed, Nov 23, 2022 at 08:24:37PM +0100, Daniel Vetter wrote: > > > It's a bit a FAQ, and we really can't claim to be the authoritative > > > source for all

Re: [PATCH] drm/fourcc: Document open source user waiver

2022-12-01 Thread Daniel Vetter
On Thu, 1 Dec 2022 at 11:07, Daniel Vetter wrote: > > On Wed, Nov 23, 2022 at 08:24:37PM +0100, Daniel Vetter wrote: > > It's a bit a FAQ, and we really can't claim to be the authoritative > > source for allocating these numbers used in many standard extensions > > if we tell closed source or vend

Re: [PATCH] drm/fourcc: Document open source user waiver

2022-12-01 Thread Daniel Vetter
On Wed, Nov 23, 2022 at 08:24:37PM +0100, Daniel Vetter wrote: > It's a bit a FAQ, and we really can't claim to be the authoritative > source for allocating these numbers used in many standard extensions > if we tell closed source or vendor stacks in general to go away. > > Iirc this was already c

Re: [PATCH] drm/fourcc: Document open source user waiver

2022-11-24 Thread Daniel Stone
On Wed, 23 Nov 2022 at 19:24, Daniel Vetter wrote: > It's a bit a FAQ, and we really can't claim to be the authoritative > source for allocating these numbers used in many standard extensions > if we tell closed source or vendor stacks in general to go away. > > Iirc this was already clarified in

Re: [PATCH] drm/fourcc: Document open source user waiver

2022-11-23 Thread Maxime Ripard
On Wed, Nov 23, 2022 at 08:24:37PM +0100, Daniel Vetter wrote: > It's a bit a FAQ, and we really can't claim to be the authoritative > source for allocating these numbers used in many standard extensions > if we tell closed source or vendor stacks in general to go away. > > Iirc this was already c

[PATCH] drm/fourcc: Document open source user waiver

2022-11-23 Thread Daniel Vetter
It's a bit a FAQ, and we really can't claim to be the authoritative source for allocating these numbers used in many standard extensions if we tell closed source or vendor stacks in general to go away. Iirc this was already clarified in some vulkan discussions, but I can't find that anywhere anymo