From: Owen Hilyard <ohilyard@iol.unh.edu>
To: "Honnappa Nagarahalli" <Honnappa.Nagarahalli@arm.com>,
"Tu, Lijuan" <lijuan.tu@intel.com>,
"Lincoln Lavoie" <lylavoie@iol.unh.edu>,
"Juraj Linkeš" <juraj.linkes@pantheon.tech>,
dts@dpdk.org
Subject: Schedule for DTS Improvement Working Group Meetings
Date: Fri, 17 Dec 2021 12:51:55 -0500 [thread overview]
Message-ID: <CAHx6DYC+6TyqGOew-aGx+shcqGqN-E=aGbBC0Voj74Kg7rpEVA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 810 bytes --]
Hello Everyone,
I wanted to get started on planning the 2022 meetings for the working
group.
The two easy options are:
1. Continue at the same time as previously, starting on the 5th of January.
I think that this would be best if we think there will be a lot of
discussions and we will need an hour to get through all of it.
2. Integrate with the CI Committee meetings
This would be best if we don't anticipate having much to discuss
every week, and we would still have the option of scheduling sessions to
deal with larger issues.
I personally won't be able to attend the full CI committee meeting until
June, due to scheduling conflicts.
Due to both my personal scheduling conflicts and anticipation of a lot more
interest in the working group, my preference is for the first option.
Owen Hilyard
[-- Attachment #2: Type: text/html, Size: 1074 bytes --]
reply other threads:[~2021-12-17 17:52 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='CAHx6DYC+6TyqGOew-aGx+shcqGqN-E=aGbBC0Voj74Kg7rpEVA@mail.gmail.com' \
--to=ohilyard@iol.unh.edu \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=dts@dpdk.org \
--cc=juraj.linkes@pantheon.tech \
--cc=lijuan.tu@intel.com \
--cc=lylavoie@iol.unh.edu \
/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).