* [PATCH] test/kms_content_protection: Use generic debugfs name for HDCP caps
@ 2019-09-23 18:23 Bhawanpreet Lakha
2019-09-24 9:54 ` [igt-dev] " Petri Latvala
2019-10-21 19:42 ` [PATCH i-g-t v2] tests/kms_content_protection: check i915 and " Bhawanpreet Lakha
0 siblings, 2 replies; 11+ messages in thread
From: Bhawanpreet Lakha @ 2019-09-23 18:23 UTC (permalink / raw)
To: igt-dev, intel-gfx; +Cc: Bhawanpreet Lakha
Rename "i915_hdcp_sink_capability" to "hdcp_sink_capability"
The content protection tests only start if this debugfs entry exists.
Since the name is specific to intel driver these tests cannot be used with
other drivers.
Remove "i915" so the debugfs name is generic.
Signed-off-by: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>
---
tests/kms_content_protection.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/kms_content_protection.c b/tests/kms_content_protection.c
index e676b60b..a105c5de 100644
--- a/tests/kms_content_protection.c
+++ b/tests/kms_content_protection.c
@@ -554,7 +554,7 @@ static bool sink_hdcp_capable(igt_output_t *output)
if (fd < 0)
return false;
- debugfs_read(fd, "i915_hdcp_sink_capability", buf);
+ debugfs_read(fd, "hdcp_sink_capability", buf);
close(fd);
igt_debug("Sink capability: %s\n", buf);
@@ -571,7 +571,7 @@ static bool sink_hdcp2_capable(igt_output_t *output)
if (fd < 0)
return false;
- debugfs_read(fd, "i915_hdcp_sink_capability", buf);
+ debugfs_read(fd, "hdcp_sink_capability", buf);
close(fd);
igt_debug("Sink capability: %s\n", buf);
--
2.17.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 11+ messages in thread* Re: [igt-dev] [PATCH] test/kms_content_protection: Use generic debugfs name for HDCP caps
2019-09-23 18:23 [PATCH] test/kms_content_protection: Use generic debugfs name for HDCP caps Bhawanpreet Lakha
@ 2019-09-24 9:54 ` Petri Latvala
2019-09-24 14:41 ` Lakha, Bhawanpreet
2019-09-24 15:41 ` Ramalingam C
2019-10-21 19:42 ` [PATCH i-g-t v2] tests/kms_content_protection: check i915 and " Bhawanpreet Lakha
1 sibling, 2 replies; 11+ messages in thread
From: Petri Latvala @ 2019-09-24 9:54 UTC (permalink / raw)
To: Bhawanpreet Lakha, Ramalingam C; +Cc: igt-dev, intel-gfx
On Mon, Sep 23, 2019 at 02:23:25PM -0400, Bhawanpreet Lakha wrote:
> Rename "i915_hdcp_sink_capability" to "hdcp_sink_capability"
>
> The content protection tests only start if this debugfs entry exists.
> Since the name is specific to intel driver these tests cannot be used with
> other drivers.
>
> Remove "i915" so the debugfs name is generic.
I don't see any drivers currently using the name
"hdcp_sink_capability". Is the content of the file in other drivers
the same as i915's?
And is there a plan to rename i915's debugfs filename to
hdcp_sink_capability? Ram?
Agreed, for a DRIVER_ANY-using test generic names are preferrable, but
this needs some kind of a transition plan. If i915's filename is
staying as is, both names need to be tried.
--
Petri Latvala
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [igt-dev] [PATCH] test/kms_content_protection: Use generic debugfs name for HDCP caps
2019-09-24 9:54 ` [igt-dev] " Petri Latvala
@ 2019-09-24 14:41 ` Lakha, Bhawanpreet
2019-09-24 15:41 ` Ramalingam C
1 sibling, 0 replies; 11+ messages in thread
From: Lakha, Bhawanpreet @ 2019-09-24 14:41 UTC (permalink / raw)
To: Ramalingam C
Cc: igt-dev@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
We have used the tests for our hdcp implementation. But because of the
name we can't use it as is.
Bhawan
On 2019-09-24 5:54 a.m., Petri Latvala wrote:
> On Mon, Sep 23, 2019 at 02:23:25PM -0400, Bhawanpreet Lakha wrote:
>> Rename "i915_hdcp_sink_capability" to "hdcp_sink_capability"
>>
>> The content protection tests only start if this debugfs entry exists.
>> Since the name is specific to intel driver these tests cannot be used with
>> other drivers.
>>
>> Remove "i915" so the debugfs name is generic.
> I don't see any drivers currently using the name
> "hdcp_sink_capability". Is the content of the file in other drivers
> the same as i915's?
>
> And is there a plan to rename i915's debugfs filename to
> hdcp_sink_capability? Ram?
>
> Agreed, for a DRIVER_ANY-using test generic names are preferrable, but
> this needs some kind of a transition plan. If i915's filename is
> staying as is, both names need to be tried.
>
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [igt-dev] [PATCH] test/kms_content_protection: Use generic debugfs name for HDCP caps
2019-09-24 9:54 ` [igt-dev] " Petri Latvala
2019-09-24 14:41 ` Lakha, Bhawanpreet
@ 2019-09-24 15:41 ` Ramalingam C
1 sibling, 0 replies; 11+ messages in thread
From: Ramalingam C @ 2019-09-24 15:41 UTC (permalink / raw)
To: Bhawanpreet Lakha, igt-dev, intel-gfx, Daniel Vetter
On 2019-09-24 at 12:54:54 +0300, Petri Latvala wrote:
> On Mon, Sep 23, 2019 at 02:23:25PM -0400, Bhawanpreet Lakha wrote:
> > Rename "i915_hdcp_sink_capability" to "hdcp_sink_capability"
> >
> > The content protection tests only start if this debugfs entry exists.
> > Since the name is specific to intel driver these tests cannot be used with
> > other drivers.
> >
> > Remove "i915" so the debugfs name is generic.
>
> I don't see any drivers currently using the name
> "hdcp_sink_capability". Is the content of the file in other drivers
> the same as i915's?
>
> And is there a plan to rename i915's debugfs filename to
> hdcp_sink_capability? Ram?
>
> Agreed, for a DRIVER_ANY-using test generic names are preferrable, but
> this needs some kind of a transition plan. If i915's filename is
> staying as is, both names need to be tried.
This IGT test change has to wait untill we have the
i915_hdcp_sink_capabilities renamed, if at all we rename.
Else based on drm_device we could decide the debugfs file and read it.
Daniel,
Considering all other debugfs are prefixed with i915, could we rename this
debugfs as "hdcp_sink_capabilities" instead?
-Ram
>
>
> --
> Petri Latvala
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 11+ messages in thread
* [PATCH i-g-t v2] tests/kms_content_protection: check i915 and generic debugfs name for HDCP caps
2019-09-23 18:23 [PATCH] test/kms_content_protection: Use generic debugfs name for HDCP caps Bhawanpreet Lakha
2019-09-24 9:54 ` [igt-dev] " Petri Latvala
@ 2019-10-21 19:42 ` Bhawanpreet Lakha
2019-10-23 14:18 ` Harry Wentland
` (2 more replies)
1 sibling, 3 replies; 11+ messages in thread
From: Bhawanpreet Lakha @ 2019-10-21 19:42 UTC (permalink / raw)
To: igt-dev; +Cc: Bhawanpreet Lakha, intel-gfx, harry.wentland
The content protection tests only start if this debugfs entry exists.
Since the name is specific to intel driver these tests cannot be used with
other drivers. So we should check generic debugfs name also
v2: Check i915_* if device is i915, otherwise check the generic name.
Signed-off-by: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>
---
tests/kms_content_protection.c | 12 ++++++++++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/tests/kms_content_protection.c b/tests/kms_content_protection.c
index e676b60b..42fdc459 100644
--- a/tests/kms_content_protection.c
+++ b/tests/kms_content_protection.c
@@ -554,7 +554,11 @@ static bool sink_hdcp_capable(igt_output_t *output)
if (fd < 0)
return false;
- debugfs_read(fd, "i915_hdcp_sink_capability", buf);
+ if (is_i915_device(data.drm_fd))
+ debugfs_read(fd, "i915_hdcp_sink_capability", buf);
+ else
+ debugfs_read(fd, "hdcp_sink_capability", buf);
+
close(fd);
igt_debug("Sink capability: %s\n", buf);
@@ -571,7 +575,11 @@ static bool sink_hdcp2_capable(igt_output_t *output)
if (fd < 0)
return false;
- debugfs_read(fd, "i915_hdcp_sink_capability", buf);
+ if (is_i915_device(data.drm_fd))
+ debugfs_read(fd, "i915_hdcp_sink_capability", buf);
+ else
+ debugfs_read(fd, "hdcp_sink_capability", buf);
+
close(fd);
igt_debug("Sink capability: %s\n", buf);
--
2.17.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 11+ messages in thread* Re: [PATCH i-g-t v2] tests/kms_content_protection: check i915 and generic debugfs name for HDCP caps
2019-10-21 19:42 ` [PATCH i-g-t v2] tests/kms_content_protection: check i915 and " Bhawanpreet Lakha
@ 2019-10-23 14:18 ` Harry Wentland
2019-10-23 14:18 ` [Intel-gfx] " Harry Wentland
2019-10-23 15:27 ` Ramalingam C
2019-10-24 11:17 ` Petri Latvala
2 siblings, 1 reply; 11+ messages in thread
From: Harry Wentland @ 2019-10-23 14:18 UTC (permalink / raw)
To: Lakha, Bhawanpreet, igt-dev@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org, Wentland, Harry
On 2019-10-21 3:42 p.m., Bhawanpreet Lakha wrote:
> The content protection tests only start if this debugfs entry exists.
> Since the name is specific to intel driver these tests cannot be used with
> other drivers. So we should check generic debugfs name also
>
> v2: Check i915_* if device is i915, otherwise check the generic name.
>
> Signed-off-by: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>
Reviewed-by: Harry Wentland <harry.wentland@amd.com>
Harry
> ---
> tests/kms_content_protection.c | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/tests/kms_content_protection.c b/tests/kms_content_protection.c
> index e676b60b..42fdc459 100644
> --- a/tests/kms_content_protection.c
> +++ b/tests/kms_content_protection.c
> @@ -554,7 +554,11 @@ static bool sink_hdcp_capable(igt_output_t *output)
> if (fd < 0)
> return false;
>
> - debugfs_read(fd, "i915_hdcp_sink_capability", buf);
> + if (is_i915_device(data.drm_fd))
> + debugfs_read(fd, "i915_hdcp_sink_capability", buf);
> + else
> + debugfs_read(fd, "hdcp_sink_capability", buf);
> +
> close(fd);
>
> igt_debug("Sink capability: %s\n", buf);
> @@ -571,7 +575,11 @@ static bool sink_hdcp2_capable(igt_output_t *output)
> if (fd < 0)
> return false;
>
> - debugfs_read(fd, "i915_hdcp_sink_capability", buf);
> + if (is_i915_device(data.drm_fd))
> + debugfs_read(fd, "i915_hdcp_sink_capability", buf);
> + else
> + debugfs_read(fd, "hdcp_sink_capability", buf);
> +
> close(fd);
>
> igt_debug("Sink capability: %s\n", buf);
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [Intel-gfx] [PATCH i-g-t v2] tests/kms_content_protection: check i915 and generic debugfs name for HDCP caps
2019-10-23 14:18 ` Harry Wentland
@ 2019-10-23 14:18 ` Harry Wentland
0 siblings, 0 replies; 11+ messages in thread
From: Harry Wentland @ 2019-10-23 14:18 UTC (permalink / raw)
To: Lakha, Bhawanpreet, igt-dev@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org, Wentland, Harry
On 2019-10-21 3:42 p.m., Bhawanpreet Lakha wrote:
> The content protection tests only start if this debugfs entry exists.
> Since the name is specific to intel driver these tests cannot be used with
> other drivers. So we should check generic debugfs name also
>
> v2: Check i915_* if device is i915, otherwise check the generic name.
>
> Signed-off-by: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>
Reviewed-by: Harry Wentland <harry.wentland@amd.com>
Harry
> ---
> tests/kms_content_protection.c | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/tests/kms_content_protection.c b/tests/kms_content_protection.c
> index e676b60b..42fdc459 100644
> --- a/tests/kms_content_protection.c
> +++ b/tests/kms_content_protection.c
> @@ -554,7 +554,11 @@ static bool sink_hdcp_capable(igt_output_t *output)
> if (fd < 0)
> return false;
>
> - debugfs_read(fd, "i915_hdcp_sink_capability", buf);
> + if (is_i915_device(data.drm_fd))
> + debugfs_read(fd, "i915_hdcp_sink_capability", buf);
> + else
> + debugfs_read(fd, "hdcp_sink_capability", buf);
> +
> close(fd);
>
> igt_debug("Sink capability: %s\n", buf);
> @@ -571,7 +575,11 @@ static bool sink_hdcp2_capable(igt_output_t *output)
> if (fd < 0)
> return false;
>
> - debugfs_read(fd, "i915_hdcp_sink_capability", buf);
> + if (is_i915_device(data.drm_fd))
> + debugfs_read(fd, "i915_hdcp_sink_capability", buf);
> + else
> + debugfs_read(fd, "hdcp_sink_capability", buf);
> +
> close(fd);
>
> igt_debug("Sink capability: %s\n", buf);
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH i-g-t v2] tests/kms_content_protection: check i915 and generic debugfs name for HDCP caps
2019-10-21 19:42 ` [PATCH i-g-t v2] tests/kms_content_protection: check i915 and " Bhawanpreet Lakha
2019-10-23 14:18 ` Harry Wentland
@ 2019-10-23 15:27 ` Ramalingam C
2019-10-23 15:27 ` [Intel-gfx] " Ramalingam C
2019-10-24 11:17 ` Petri Latvala
2 siblings, 1 reply; 11+ messages in thread
From: Ramalingam C @ 2019-10-23 15:27 UTC (permalink / raw)
To: Bhawanpreet Lakha; +Cc: igt-dev, intel-gfx, harry.wentland
On 2019-10-21 at 15:42:59 -0400, Bhawanpreet Lakha wrote:
> The content protection tests only start if this debugfs entry exists.
> Since the name is specific to intel driver these tests cannot be used with
> other drivers. So we should check generic debugfs name also
>
> v2: Check i915_* if device is i915, otherwise check the generic name.
>
> Signed-off-by: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>
Looks good to me.
Reviewed-by: Ramalingam C <ramalingam.c@intel.com>
> ---
> tests/kms_content_protection.c | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/tests/kms_content_protection.c b/tests/kms_content_protection.c
> index e676b60b..42fdc459 100644
> --- a/tests/kms_content_protection.c
> +++ b/tests/kms_content_protection.c
> @@ -554,7 +554,11 @@ static bool sink_hdcp_capable(igt_output_t *output)
> if (fd < 0)
> return false;
>
> - debugfs_read(fd, "i915_hdcp_sink_capability", buf);
> + if (is_i915_device(data.drm_fd))
> + debugfs_read(fd, "i915_hdcp_sink_capability", buf);
> + else
> + debugfs_read(fd, "hdcp_sink_capability", buf);
> +
> close(fd);
>
> igt_debug("Sink capability: %s\n", buf);
> @@ -571,7 +575,11 @@ static bool sink_hdcp2_capable(igt_output_t *output)
> if (fd < 0)
> return false;
>
> - debugfs_read(fd, "i915_hdcp_sink_capability", buf);
> + if (is_i915_device(data.drm_fd))
> + debugfs_read(fd, "i915_hdcp_sink_capability", buf);
> + else
> + debugfs_read(fd, "hdcp_sink_capability", buf);
> +
> close(fd);
>
> igt_debug("Sink capability: %s\n", buf);
> --
> 2.17.1
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [Intel-gfx] [PATCH i-g-t v2] tests/kms_content_protection: check i915 and generic debugfs name for HDCP caps
2019-10-23 15:27 ` Ramalingam C
@ 2019-10-23 15:27 ` Ramalingam C
0 siblings, 0 replies; 11+ messages in thread
From: Ramalingam C @ 2019-10-23 15:27 UTC (permalink / raw)
To: Bhawanpreet Lakha; +Cc: igt-dev, intel-gfx, harry.wentland
On 2019-10-21 at 15:42:59 -0400, Bhawanpreet Lakha wrote:
> The content protection tests only start if this debugfs entry exists.
> Since the name is specific to intel driver these tests cannot be used with
> other drivers. So we should check generic debugfs name also
>
> v2: Check i915_* if device is i915, otherwise check the generic name.
>
> Signed-off-by: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>
Looks good to me.
Reviewed-by: Ramalingam C <ramalingam.c@intel.com>
> ---
> tests/kms_content_protection.c | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/tests/kms_content_protection.c b/tests/kms_content_protection.c
> index e676b60b..42fdc459 100644
> --- a/tests/kms_content_protection.c
> +++ b/tests/kms_content_protection.c
> @@ -554,7 +554,11 @@ static bool sink_hdcp_capable(igt_output_t *output)
> if (fd < 0)
> return false;
>
> - debugfs_read(fd, "i915_hdcp_sink_capability", buf);
> + if (is_i915_device(data.drm_fd))
> + debugfs_read(fd, "i915_hdcp_sink_capability", buf);
> + else
> + debugfs_read(fd, "hdcp_sink_capability", buf);
> +
> close(fd);
>
> igt_debug("Sink capability: %s\n", buf);
> @@ -571,7 +575,11 @@ static bool sink_hdcp2_capable(igt_output_t *output)
> if (fd < 0)
> return false;
>
> - debugfs_read(fd, "i915_hdcp_sink_capability", buf);
> + if (is_i915_device(data.drm_fd))
> + debugfs_read(fd, "i915_hdcp_sink_capability", buf);
> + else
> + debugfs_read(fd, "hdcp_sink_capability", buf);
> +
> close(fd);
>
> igt_debug("Sink capability: %s\n", buf);
> --
> 2.17.1
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH i-g-t v2] tests/kms_content_protection: check i915 and generic debugfs name for HDCP caps
2019-10-21 19:42 ` [PATCH i-g-t v2] tests/kms_content_protection: check i915 and " Bhawanpreet Lakha
2019-10-23 14:18 ` Harry Wentland
2019-10-23 15:27 ` Ramalingam C
@ 2019-10-24 11:17 ` Petri Latvala
2019-10-24 11:17 ` [Intel-gfx] " Petri Latvala
2 siblings, 1 reply; 11+ messages in thread
From: Petri Latvala @ 2019-10-24 11:17 UTC (permalink / raw)
To: Bhawanpreet Lakha; +Cc: igt-dev, intel-gfx, harry.wentland
On Mon, Oct 21, 2019 at 03:42:59PM -0400, Bhawanpreet Lakha wrote:
> The content protection tests only start if this debugfs entry exists.
> Since the name is specific to intel driver these tests cannot be used with
> other drivers. So we should check generic debugfs name also
>
> v2: Check i915_* if device is i915, otherwise check the generic name.
>
> Signed-off-by: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>
Merged, thanks for the patch and reviews!
--
Petri Latvala
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Intel-gfx] [PATCH i-g-t v2] tests/kms_content_protection: check i915 and generic debugfs name for HDCP caps
2019-10-24 11:17 ` Petri Latvala
@ 2019-10-24 11:17 ` Petri Latvala
0 siblings, 0 replies; 11+ messages in thread
From: Petri Latvala @ 2019-10-24 11:17 UTC (permalink / raw)
To: Bhawanpreet Lakha; +Cc: igt-dev, intel-gfx, harry.wentland
On Mon, Oct 21, 2019 at 03:42:59PM -0400, Bhawanpreet Lakha wrote:
> The content protection tests only start if this debugfs entry exists.
> Since the name is specific to intel driver these tests cannot be used with
> other drivers. So we should check generic debugfs name also
>
> v2: Check i915_* if device is i915, otherwise check the generic name.
>
> Signed-off-by: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>
Merged, thanks for the patch and reviews!
--
Petri Latvala
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2019-10-24 11:17 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-09-23 18:23 [PATCH] test/kms_content_protection: Use generic debugfs name for HDCP caps Bhawanpreet Lakha
2019-09-24 9:54 ` [igt-dev] " Petri Latvala
2019-09-24 14:41 ` Lakha, Bhawanpreet
2019-09-24 15:41 ` Ramalingam C
2019-10-21 19:42 ` [PATCH i-g-t v2] tests/kms_content_protection: check i915 and " Bhawanpreet Lakha
2019-10-23 14:18 ` Harry Wentland
2019-10-23 14:18 ` [Intel-gfx] " Harry Wentland
2019-10-23 15:27 ` Ramalingam C
2019-10-23 15:27 ` [Intel-gfx] " Ramalingam C
2019-10-24 11:17 ` Petri Latvala
2019-10-24 11:17 ` [Intel-gfx] " Petri Latvala
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox