Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: Romain Naour <romain.naour@smile.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] support/testing: test_clang: update to the next LTS kernel (4.19.x)
Date: Sat, 3 Jun 2023 21:30:19 +0200	[thread overview]
Message-ID: <20230603213019.7da071b0@windsurf> (raw)
In-Reply-To: <510ba693-7acd-74cc-8f8f-c961fd34d20a@mind.be>

Hello,

On Sat, 3 Jun 2023 21:21:10 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:

>   We should really create more downloadable kernel and rely on those instead of 
> building the kernel during the runtime test. It takes a lot of time with no 
> merit. Unfortunately, those are on abo which only Thomas has access to...

I will be happy to update those binaries if need be, and also there is
nothing that really prevents from changing the location where those
files are hosted.

Best regards,

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

  reply	other threads:[~2023-06-03 19:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-24 13:16 [Buildroot] [PATCH] support/testing: test_clang: update to the next LTS kernel (4.19.x) Romain Naour
2023-06-03 19:21 ` Arnout Vandecappelle via buildroot
2023-06-03 19:30   ` Thomas Petazzoni via buildroot [this message]
2023-06-14 11:51 ` Peter Korsgaard

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=20230603213019.7da071b0@windsurf \
    --to=buildroot@buildroot.org \
    --cc=arnout@mind.be \
    --cc=romain.naour@smile.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox