From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Julien Olivain <ju.o@free.fr>, Adam Duskett <aduskett@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 0/2 v2] support/runtime-test: extend graphic testing for weston + flutter (branch yem/flutter)
Date: Wed, 7 Aug 2024 22:57:19 +0200 [thread overview]
Message-ID: <20240807225719.42d8a4c1@windsurf> (raw)
In-Reply-To: <cover.1696522656.git.yann.morin.1998@free.fr>
Hello,
On Thu, 5 Oct 2023 18:17:38 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> Yann E. MORIN (2):
> support/runtime-test: add helper to test graphics rendering
> suport/runtime-test: extend flutter test to check rendering is happening
Thanks, I have applied this series!
Some changes:
- On PATCH 1/2, I made an addition to the DEVELOPERS to add you (Yann)
as the contact for the graphics base class
- On PATCH 2/2, some rebasing was needed, as the test case no longer
uses flutter-gallery, but flutter-markdown-example
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-08-07 20:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 16:17 [Buildroot] [PATCH 0/2 v2] support/runtime-test: extend graphic testing for weston + flutter (branch yem/flutter) Yann E. MORIN
2023-10-05 16:17 ` [Buildroot] [PATCH 1/2 v2] support/runtime-test: add helper to test graphics rendering Yann E. MORIN
2023-10-06 20:15 ` Julien Olivain
2023-10-05 16:17 ` [Buildroot] [PATCH 2/2 v2] suport/runtime-test: extend flutter test to check rendering is happening Yann E. MORIN
2023-10-06 11:11 ` Adam Duskett
2024-08-07 20:57 ` Thomas Petazzoni via buildroot [this message]
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=20240807225719.42d8a4c1@windsurf \
--to=buildroot@buildroot.org \
--cc=aduskett@gmail.com \
--cc=ju.o@free.fr \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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.