From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: dts@dpdk.org, ci@dpdk.org
Subject: [dts] DTS Usability and Developer Feedback
Date: Wed, 23 Sep 2020 08:36:16 -0400 [thread overview]
Message-ID: <CAOE1vsPS3G7bimuycP_g1AMAVA5FPGQh6xD=uDQ2bjugKWB-nA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 709 bytes --]
Hello All,
On our last CI call, there was a request to start collecting feedback on
DTS from a user and developer perspective. I've started a document at the
link below and my team has added their initial feedback. The goal is to
collect as much info as possible, so don't worry about polishing your
comments. We'll distill the input after it's all collected.
https://docs.google.com/document/d/1c5S0_mZzFvzZfYkqyORLT2-qNvUb-fBdjA6DGusy4yM/edit
Please let me know if you have any questions.
Cheers,
Lincoln
--
*Lincoln Lavoie*
Senior Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, Durham, NH 03824
lylavoie@iol.unh.edu
https://www.iol.unh.edu
+1-603-674-2755 (m)
<https://www.iol.unh.edu>
[-- Attachment #2: Type: text/html, Size: 1997 bytes --]
reply other threads:[~2020-09-23 12:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAOE1vsPS3G7bimuycP_g1AMAVA5FPGQh6xD=uDQ2bjugKWB-nA@mail.gmail.com' \
--to=lylavoie@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=dts@dpdk.org \
/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).