From: Patrick Robb <probb@iol.unh.edu>
To: jspewock@iol.unh.edu
Cc: Honnappa.Nagarahalli@arm.com, juraj.linkes@pantheon.tech,
thomas@monjalon.net, wathsala.vithanage@arm.com,
paul.szczepanek@arm.com, yoan.picchi@foss.arm.com, dev@dpdk.org
Subject: Re: [PATCH v4] dts: add Dockerfile
Date: Tue, 20 Feb 2024 22:40:21 -0500 [thread overview]
Message-ID: <CAJvnSUCejaqZoR+3UXAiDaeOq==x-AnZVxtBDzkCFLVawUdHVw@mail.gmail.com> (raw)
In-Reply-To: <20240116191814.31316-1-jspewock@iol.unh.edu>
[-- Attachment #1: Type: text/plain, Size: 586 bytes --]
Tested-by: Patrick Robb <probb@iol.unh.edu>
The approach for mounting in ssh keys and managing the test engine
environment has been agreed upon by the CI group, and this patch has been
tested by a few people at the Community Lab. I believe it is ready to be
merged.
On Tue, Jan 16, 2024 at 2:18 PM <jspewock@iol.unh.edu> wrote:
> From: Juraj Linkeš <juraj.linkes@pantheon.tech>
>
> The Dockerfile defines development and CI runner images.
>
> Signed-off-by: Juraj Linkeš <juraj.linkes@pantheon.tech>
> Signed-off-by: Jeremy Spewock <jspewock@iol.unh.edu>
>
>
>
[-- Attachment #2: Type: text/html, Size: 1043 bytes --]
next prev parent reply other threads:[~2024-02-21 3:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 13:46 [PATCH v1] " Juraj Linkeš
2022-11-04 9:16 ` Juraj Linkeš
2023-02-09 16:49 ` Patrick Robb
2023-04-28 19:34 ` Jeremy Spewock
2023-10-17 13:52 ` Paul Szczepanek
2023-10-26 21:56 ` Jeremy Spewock
2023-10-27 9:19 ` Juraj Linkeš
2024-01-11 21:35 ` [PATCH v2] " jspewock
2024-01-11 22:26 ` [PATCH v3] " jspewock
2024-01-12 10:23 ` Juraj Linkeš
2024-01-12 14:59 ` Jeremy Spewock
2024-01-15 9:22 ` Juraj Linkeš
2024-01-16 19:18 ` [PATCH v4] " jspewock
2024-01-17 9:00 ` Juraj Linkeš
2024-02-21 3:40 ` Patrick Robb [this message]
2024-03-07 10:51 ` Thomas Monjalon
[not found] ` <CAJvnSUDDpGdxe8D-GmtbVixrrrB_GRfvS985Cw1RLx79aLcXnA@mail.gmail.com>
2024-02-29 16:14 ` Nicholas Pratte
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='CAJvnSUCejaqZoR+3UXAiDaeOq==x-AnZVxtBDzkCFLVawUdHVw@mail.gmail.com' \
--to=probb@iol.unh.edu \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=jspewock@iol.unh.edu \
--cc=juraj.linkes@pantheon.tech \
--cc=paul.szczepanek@arm.com \
--cc=thomas@monjalon.net \
--cc=wathsala.vithanage@arm.com \
--cc=yoan.picchi@foss.arm.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;
as well as URLs for NNTP newsgroup(s).