From: Paul Szczepanek <Paul.Szczepanek@arm.com>
To: "Patrick Robb" <probb@iol.unh.edu>,
"Juraj Linkeš" <juraj.linkes@pantheon.tech>,
"Honnappa Nagarahalli" <Honnappa.Nagarahalli@arm.com>,
"Luca Vizzarro" <Luca.Vizzarro@arm.com>,
"Yoan Picchi" <yoan.picchi@foss.arm.com>,
"Jeremy Spewock" <jspewock@iol.unh.edu>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"getelson@nvidia.com" <getelson@nvidia.com>
Cc: "ci@dpdk.org" <ci@dpdk.org>
Subject: Re: Regular DTS meeting scheduling
Date: Tue, 2 Jan 2024 09:26:54 +0000 [thread overview]
Message-ID: <DB4PR08MB8151B0BB90AFED392C4675FBE961A@DB4PR08MB8151.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <CAJvnSUBrKci_f3A1G47bEEtnTKxEXq26+a0wd_MTKZDnkzZYmw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1581 bytes --]
14:00-15:00 UTC Wednesdays looks great but all the times listed work for me, Yoan and Luca.
________________________________
From: Patrick Robb <probb@iol.unh.edu>
Sent: 22 December 2023 18:33
To: Juraj Linkeš <juraj.linkes@pantheon.tech>; Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>; Paul Szczepanek <Paul.Szczepanek@arm.com>; Luca Vizzarro <Luca.Vizzarro@arm.com>; Yoan Picchi <yoan.picchi@foss.arm.com>; Jeremy Spewock <jspewock@iol.unh.edu>; thomas@monjalon.net <thomas@monjalon.net>; getelson@nvidia.com <getelson@nvidia.com>
Cc: ci@dpdk.org <ci@dpdk.org>
Subject: Regular DTS meeting scheduling
Hello all DTS interested people,
I'm looking to find a good timeslot for having DTS sync calls this Spring. Obviously we want to do it on the off weeks from the CI meetings, and we want to do it in the morning USA time so that it works for EU people too.
Right now the timeslots I'm looking at are:
14:00-15:00 UTC Mondays
15:00-16:00 UTC Mondays
14:00-15:00 UTC Wednesdays
15:00-16:00 UTC Wednesdays
All else being equal, Wednesdays are probably best, as it allows for better spacing between CI meetings, but we'll do whatever works for the most people. Please feel free to indicate your availability!
Best,
Patrick
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
[-- Attachment #2: Type: text/html, Size: 2744 bytes --]
next prev parent reply other threads:[~2024-01-02 9:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 18:33 Patrick Robb
2023-12-22 22:20 ` Thomas Monjalon
2023-12-25 4:43 ` Etelson, Gregory
2024-01-02 9:26 ` Paul Szczepanek [this message]
2024-01-02 21:56 ` Honnappa Nagarahalli
2024-01-02 23:08 ` Patrick Robb
2024-01-03 10:55 ` Juraj Linkeš
2024-01-09 14:59 ` Patrick Robb
2024-01-09 15:13 ` Patrick Robb
2024-01-16 23:08 ` Patrick Robb
2024-01-17 15:10 ` Patrick Robb
2024-01-17 15:12 ` Patrick Robb
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=DB4PR08MB8151B0BB90AFED392C4675FBE961A@DB4PR08MB8151.eurprd08.prod.outlook.com \
--to=paul.szczepanek@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Luca.Vizzarro@arm.com \
--cc=ci@dpdk.org \
--cc=getelson@nvidia.com \
--cc=jspewock@iol.unh.edu \
--cc=juraj.linkes@pantheon.tech \
--cc=probb@iol.unh.edu \
--cc=thomas@monjalon.net \
--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).