From: Alexander Dahl <ada@thorsis.com>
To: Ladislav Michl <oss-lists@triops.cz>
Cc: distrokit@pengutronix.de
Subject: Re: [DistroKit] [PATCH 00/08] PTXdist & Toolchain update
Date: Wed, 10 Apr 2024 08:59:50 +0200 [thread overview]
Message-ID: <20240410-vastness-maverick-4ea60f99c8fe@thorsis.com> (raw)
In-Reply-To: <ZhPO_C8rKy-W4CVa@lenoch>
Hei hei,
Am Mon, Apr 08, 2024 at 01:03:24PM +0200 schrieb Ladislav Michl:
> Hi,
>
> a while ago I started a little toy project:
> https://github.com/3x380V/kodist
> as it lives on the edge, I think it is a time to enforce DistroKit
> to do the same. Following patches based on -next do just that.
I usually install oselas toolchain from pengutronix debian package
server and using the "base" package like
'oselas.toolchain-2023.07-aarch64-v8a-linux-gnu' or
'oselas.toolchain-2023.07-arm-v7a-linux-gnueabihf' which pulls in the
latest variant of that toolchain. So +1 for updating the toolchains!
Add my a-b for all the toolchain updates. (Did not review the ptxdist
update in detail.)
Acked-by: Alexander Dahl <ada@thorsis.com>
Greets
Alex
next prev parent reply other threads:[~2024-04-10 7:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 11:03 Ladislav Michl
2024-04-08 11:04 ` [DistroKit] [PATCH 1/8]ptxdist: migrate 2024.03.0 → 2024.04.0 Ladislav Michl
2024-04-08 11:04 ` [DistroKit] [PATCH 2/8] mipsel: update to OSELAS.Toolchain 2023.07.1 Ladislav Michl
2024-04-08 11:05 ` [DistroKit] [PATCH 3/8] mips: " Ladislav Michl
2024-04-08 11:05 ` [DistroKit] [PATCH 4/8] rpi1: " Ladislav Michl
2024-04-08 11:06 ` [DistroKit] [PATCH 5/8] v7a: " Ladislav Michl
2024-04-08 11:06 ` [DistroKit] [PATCH 6/8] v7a_noneon: " Ladislav Michl
2024-04-08 11:07 ` [DistroKit] [PATCH 7/8] v8a: " Ladislav Michl
2024-04-08 11:07 ` [DistroKit] [PATCH 8/8] x86_64: " Ladislav Michl
2024-04-10 6:59 ` Alexander Dahl [this message]
2024-04-11 10:24 ` [DistroKit] [PATCH 00/08] PTXdist & Toolchain update Ladislav Michl
2024-04-22 14:28 ` Robert Schwebel
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=20240410-vastness-maverick-4ea60f99c8fe@thorsis.com \
--to=ada@thorsis.com \
--cc=distrokit@pengutronix.de \
--cc=oss-lists@triops.cz \
/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