Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "wangmy" <wangmy@fujitsu.com>
Cc: <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] mesa: upgrade 22.0.3 -> 22.1.1
Date: Tue, 7 Jun 2022 12:40:56 +0200	[thread overview]
Message-ID: <20220607124056.78bad3b5@booty> (raw)
In-Reply-To: <1654518434-9263-3-git-send-email-wangmy@fujitsu.com>

Hi wangmy,

On Mon, 6 Jun 2022 20:27:12 +0800
"wangmy" <wangmy@fujitsu.com> wrote:

> Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>

There are lots of failures when testing with this patch applied:

  (EE) AIGLX error: Calling driver entry point failed

Here are some logs:

https://autobuilder.yoctoproject.org/typhoon/#/builders/73/builds/5275/steps/12/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/5318/steps/13/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/76/builds/5291/steps/13/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/5338/steps/19/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/109/builds/4202/steps/13/logs/stdio

-- 
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  reply	other threads:[~2022-06-07 10:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-06 12:27 [OE-core] [PATCH] nettle: upgrade 3.7.3 -> 3.8 Wang Mingyu
2022-06-06 12:27 ` [OE-core] [PATCH] kbd: upgrade 2.4.0 -> 2.5.0 Wang Mingyu
2022-06-06 12:27 ` [OE-core] [PATCH] mesa: upgrade 22.0.3 -> 22.1.1 Wang Mingyu
2022-06-07 10:40   ` Luca Ceresoli [this message]
2022-06-09 10:00     ` Alexander Kanavin
2022-06-06 12:27 ` [OE-core] [PATCH] python3-hypothesis: upgrade 6.46.9 -> 6.46.11 Wang Mingyu
2022-06-06 12:27 ` [OE-core] [PATCH] xkeyboard-config: upgrade 2.35.1 -> 2.36 Wang Mingyu

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=20220607124056.78bad3b5@booty \
    --to=luca.ceresoli@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=wangmy@fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox