From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Markus Volk" <f_l_k@t-online.de>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [oe-core][PATCH 1/4] xorg-lib-common: allow to build for wayland
Date: Fri, 3 Jun 2022 22:17:27 +0200 [thread overview]
Message-ID: <20220603221727.1e8c5f6b@booty> (raw)
In-Reply-To: <6b5c87ac-3ea0-be92-9439-7cf69d136c9b@t-online.de>
Hi Markus,
On Wed, 1 Jun 2022 17:10:45 +0200
"Markus Volk" <f_l_k@t-online.de> wrote:
> Hi Luca,
>
> i've sent a patch that should hopefully fix your issue
I guess you refer to:
[oe-core][PATCH] xorg-font-common.inc: allow to build for wayland
and so I ran a build test with the above patch + the 4 patches in this
series.
However I would find it a lot clearer if you instead sent a v2 series
with all the 5 patches (1 new + 4 as in the previous version). It would
avoid any confusion.
About the test, unfortunately we are still having failures:
https://autobuilder.yoctoproject.org/typhoon/#/builders/40/builds/5316/steps/11/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/40/builds/5316/steps/14/logs/stdio
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2022-06-03 20:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 19:06 [oe-core][PATCH 1/4] xorg-lib-common: allow to build for wayland Markus Volk
2022-05-31 19:06 ` [oe-core][PATCH 2/4] libxcb: " Markus Volk
2022-05-31 19:06 ` [oe-core][PATCH 3/4] xdg-utils: " Markus Volk
2022-05-31 19:06 ` [oe-core][PATCH 4/4] libsdl2: dont mix opengl and gles backends " Markus Volk
2022-05-31 20:54 ` richard.purdie
2022-05-31 21:06 ` Khem Raj
2022-05-31 21:13 ` Markus Volk
2022-06-01 15:00 ` [oe-core][PATCH 1/4] xorg-lib-common: allow to build " Luca Ceresoli
2022-06-01 15:10 ` Markus Volk
2022-06-03 20:17 ` Luca Ceresoli [this message]
2022-06-04 5:29 ` Markus Volk
2022-06-06 10:20 ` Ross Burton
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=20220603221727.1e8c5f6b@booty \
--to=luca.ceresoli@bootlin.com \
--cc=f_l_k@t-online.de \
--cc=openembedded-core@lists.openembedded.org \
/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.