From: Owen Hilyard <ohilyard@iol.unh.edu>
To: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
Cc: "dts@dpdk.org" <dts@dpdk.org>,
"lijuan.tu@intel.com" <lijuan.tu@intel.com>
Subject: Re: [dts] [PATCH v2] ci/initial: Added script to get the tests for a patchset
Date: Fri, 3 Sep 2021 12:49:36 -0400 [thread overview]
Message-ID: <CAHx6DYDbj7pJ_9pdSm9RUi4OU3aA_7f13nuR7_9vNZP8NuJxGQ@mail.gmail.com> (raw)
In-Reply-To: <35cfdcbff7f54d9d9e00d611d1490db8@pantheon.tech>
[-- Attachment #1: Type: text/plain, Size: 169 bytes --]
I can fix the newlines, but I don't remember any discussion about how DTS
will handle licenses. That is probably a topic for either the working group
or the tech board.
[-- Attachment #2: Type: text/html, Size: 194 bytes --]
next prev parent reply other threads:[~2021-09-03 16:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 15:36 ohilyard
2021-09-03 9:42 ` Juraj Linkeš
2021-09-03 16:49 ` Owen Hilyard [this message]
2021-10-13 14:19 ` ohilyard
2022-04-06 13:01 ` Tu, Lijuan
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=CAHx6DYDbj7pJ_9pdSm9RUi4OU3aA_7f13nuR7_9vNZP8NuJxGQ@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).