mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Dahl <ada@thorsis.com>
To: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Docker rules
Date: Fri, 18 Mar 2022 08:36:26 +0100	[thread overview]
Message-ID: <YjQ2egNu4TtCyZZz@ada-deb-carambola.ifak-system.com> (raw)
In-Reply-To: <3ed5bbe3-0179-dd6a-ed73-7dff60c5676d@metux.net>

Hallo Enrico,

Am Thu, Mar 17, 2022 at 05:00:57PM +0100 schrieb Enrico Weigelt, metux IT consult:
> On 27.01.22 18:22, Alexander Dahl wrote:
> > Hello Mircea,
> > 
> > On Thu, Jan 27, 2022 at 05:37:01PM +0100, Mircea Ciocan wrote:
> > > are there any official or unofficial rules to have docker container support
> > > build with PTXDist on aarch64 platforms
> > 
> > Do you mean running Docker containers on the target?  Or buildung a
> > ptxdist based BSP in a Docker container?  AFAIK there's neither one or
> > the other.
> 
> actually did exactly this (both docker on the target as well as building
> docker images via ptxdist) about a year ago ... not sure wether my
> patches reached this list ...

Could not find them at https://lore.ptxdist.org/ptxdist/?q=docker …
(also not with different search terms).

Sure you send it?  I could also not find it in my personal archive.

Alex

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de

      reply	other threads:[~2022-03-18  7:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27 16:37 Mircea Ciocan
2022-01-27 17:22 ` Alexander Dahl
2022-01-28 11:01   ` Michael Olbrich
2022-01-28 11:15     ` Felix Mellmann
2022-01-28 11:15     ` Felix Mellmann
2022-01-28 12:40     ` Christian Melki
2022-01-28 15:18   ` Mircea Ciocan
2022-03-17 16:00   ` Enrico Weigelt, metux IT consult
2022-03-18  7:36     ` Alexander Dahl [this message]

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=YjQ2egNu4TtCyZZz@ada-deb-carambola.ifak-system.com \
    --to=ada@thorsis.com \
    --cc=lkml@metux.net \
    --cc=ptxdist@pengutronix.de \
    /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