From 642dd7af507d8f1c618b8a1397aba649681f8bcd Mon Sep 17 00:00:00 2001 From: Varad Gautam Date: Mon, 21 Nov 2016 15:47:22 +0530 Subject: linux-dmabuf: clarify format event description clearly state the request name in format event to avoid abmiguous interpretation between 'zwp_linux_buffer_params_v1::create' and 'zwp_linux_dmabuf_v1::create_params' requests. v2: grammar fixup (Yong Bakos) Signed-off-by: Varad Gautam Suggested-by: Yong Bakos Reviewed-by: Yong Bakos Reviewed-by: Daniel Stone --- unstable/linux-dmabuf/linux-dmabuf-unstable-v1.xml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'unstable') diff --git a/unstable/linux-dmabuf/linux-dmabuf-unstable-v1.xml b/unstable/linux-dmabuf/linux-dmabuf-unstable-v1.xml index a07540e..60240f9 100644 --- a/unstable/linux-dmabuf/linux-dmabuf-unstable-v1.xml +++ b/unstable/linux-dmabuf/linux-dmabuf-unstable-v1.xml @@ -98,7 +98,8 @@ binds to this interface. A roundtrip after binding guarantees that the client has received all supported formats. - For the definition of the format codes, see create request. + For the definition of the format codes, see the + zwp_linux_buffer_params_v1::create request. XXX: Can a compositor ever enumerate them? -- cgit v1.2.3