DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: jspewock@iol.unh.edu, juraj.linkes@pantheon.tech,
	Patrick Robb <probb@iol.unh.edu>
Cc: dev@dpdk.org, Honnappa.Nagarahalli@arm.com,
	wathsala.vithanage@arm.com, paul.szczepanek@arm.com,
	yoan.picchi@foss.arm.com
Subject: Re: [PATCH v4] dts: add Dockerfile
Date: Thu, 07 Mar 2024 11:51:09 +0100	[thread overview]
Message-ID: <2747802.9PvXe5no7K@thomas> (raw)
In-Reply-To: <CAJvnSUCejaqZoR+3UXAiDaeOq==x-AnZVxtBDzkCFLVawUdHVw@mail.gmail.com>

21/02/2024 04:40, Patrick Robb:
> 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.

Applied, thanks.

Note: few minor adjustments were made in the README and devtools.



  reply	other threads:[~2024-03-07 10:51 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
2024-03-07 10:51         ` Thomas Monjalon [this message]
     [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=2747802.9PvXe5no7K@thomas \
    --to=thomas@monjalon.net \
    --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=probb@iol.unh.edu \
    --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).