Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Romain Naour <romain.naour@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] support/testing: TestGlxinfo: bump kernel version to 6.1.x
Date: Wed, 12 Jul 2023 12:05:57 +0200	[thread overview]
Message-ID: <20230712120557.143513ff@windsurf> (raw)
In-Reply-To: <20230611115748.801929-1-romain.naour@gmail.com>

Hello Romain,

On Sun, 11 Jun 2023 13:57:47 +0200
Romain Naour <romain.naour@gmail.com> wrote:

> The kernel 6.1.x is the latest LTS version.
> 
> Signed-off-by: Romain Naour <romain.naour@gmail.com>
> ---
>  support/testing/tests/package/test_glxinfo.py | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Thanks, I've applied both. However, did you notice that this GlxInfo
test is currently broken? See
https://gitlab.com/buildroot.org/buildroot/-/jobs/4621046326. It fails
at runtime because the glxinfo command cannot be found in the
filesystem (I have not investigated further than that).

Best regards,

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-12 10:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-11 11:57 [Buildroot] [PATCH 1/2] support/testing: TestGlxinfo: bump kernel version to 6.1.x Romain Naour
2023-06-11 11:57 ` [Buildroot] [PATCH 2/2] support/testing: TestGlxinfo: bump the toolchain to x86 core2 Bootlin toolchain stable 2022.08-1 Romain Naour
2023-07-12 10:05 ` Thomas Petazzoni via buildroot [this message]
2023-07-12 12:52   ` [Buildroot] [PATCH 1/2] support/testing: TestGlxinfo: bump kernel version to 6.1.x Romain Naour
2023-07-12 14:09     ` Romain Naour
2023-07-12 14:40       ` Thomas Petazzoni via buildroot

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=20230712120557.143513ff@windsurf \
    --to=buildroot@buildroot.org \
    --cc=romain.naour@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox