From: Owen Hilyard <ohilyard@iol.unh.edu>
To: dts@dpdk.org
Cc: "Tu, Lijuan" <lijuan.tu@intel.com>,
"Juraj Linkeš" <juraj.linkes@pantheon.tech>
Subject: Re: [PATCH v2 2/2] update files depending on tests/util
Date: Mon, 11 Apr 2022 13:57:23 -0400 [thread overview]
Message-ID: <CAHx6DYD_FAWbn=v-iN9ZpNebMctDzeZHxzOgVkYWbixP95z5fA@mail.gmail.com> (raw)
In-Reply-To: <20220411175549.14680-2-ohilyard@iol.unh.edu>
[-- Attachment #1: Type: text/plain, Size: 94 bytes --]
Sorry about that, it looks like I missed the second commit when I sent it
out the first time.
[-- Attachment #2: Type: text/html, Size: 139 bytes --]
next prev parent reply other threads:[~2022-04-11 17:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 17:55 [PATCH v2 1/2] framework: Move test-specific files to test directory ohilyard
2022-04-11 17:55 ` [PATCH v2 2/2] update files depending on tests/util ohilyard
2022-04-11 17:57 ` Owen Hilyard [this message]
2022-04-13 7:28 ` Juraj Linkeš
2022-04-13 12:50 ` Owen Hilyard
2022-04-13 7:25 ` [PATCH v2 1/2] framework: Move test-specific files to test directory Juraj Linkeš
2022-04-13 12:50 ` Owen Hilyard
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='CAHx6DYD_FAWbn=v-iN9ZpNebMctDzeZHxzOgVkYWbixP95z5fA@mail.gmail.com' \
--to=ohilyard@iol.unh.edu \
--cc=dts@dpdk.org \
--cc=juraj.linkes@pantheon.tech \
--cc=lijuan.tu@intel.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).