All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/glslsandbox-player: bump to version v2023.04.05
Date: Sat, 29 Jul 2023 23:39:27 +0200	[thread overview]
Message-ID: <20230729233927.572fd26c@windsurf> (raw)
In-Reply-To: <20230607202439.188050-1-ju.o@free.fr>

Hello Julien,

On Wed,  7 Jun 2023 22:24:38 +0200
Julien Olivain <ju.o@free.fr> wrote:

> License hash changed due to copyright year update.
> 
> Signed-off-by: Julien Olivain <ju.o@free.fr>
> ---
>  package/glslsandbox-player/glslsandbox-player.hash | 4 ++--
>  package/glslsandbox-player/glslsandbox-player.mk   | 2 +-
>  2 files changed, 3 insertions(+), 3 deletions(-)

Both applied to master. Nice to see an OpenGL test case in automated
tests! I'm curious to understand more how it works:

- How does glslsandboxplayer knows that we want the frames to be
  generated as .ppm files?

- What role does the DRM vkms driver play in the story?

Thanks for this work!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2023-07-29 21:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-07 20:24 [Buildroot] [PATCH 1/2] package/glslsandbox-player: bump to version v2023.04.05 Julien Olivain
2023-06-07 20:24 ` [Buildroot] [PATCH 2/2] support/testing/tests/package/test_glslsandbox_player.py: new runtime test Julien Olivain
2023-07-29 21:39 ` Thomas Petazzoni via buildroot [this message]
2023-07-30 12:12   ` [Buildroot] [PATCH 1/2] package/glslsandbox-player: bump to version v2023.04.05 Julien Olivain
2023-07-30 14:06     ` Thomas Petazzoni via buildroot
2023-07-30 15:08     ` Julien Olivain

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230729233927.572fd26c@windsurf \
    --to=buildroot@buildroot.org \
    --cc=ju.o@free.fr \
    --cc=thomas.petazzoni@bootlin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.