From: Julien Grall <julien.grall@linaro.org>
To: xen-devel <xen-devel@lists.xenproject.org>,
"Edgar E. Iglesias" <edgar.iglesias@xilinx.com>,
lars.kurth@citrix.com, scampbel@codeaurora.org,
stewart.Hildebrand@dornerworks.com,
Stefano Stabellini <sstabellini@kernel.org>,
anastassios.nanos@onapp.com, sgoel@codeaurora.org,
vfachin@de.adit-jv.com,
Jarvis Roach <Jarvis.Roach@dornerworks.com>,
volodymyr_babchuk@epam.com,
Artem Mygaiev <Artem_Mygaiev@epam.com>
Subject: Next Xen Arm Community call - Wednesday 22nd November
Date: Thu, 16 Nov 2017 11:54:51 +0000 [thread overview]
Message-ID: <92b77e94-00ff-d81b-e4e0-bb7cf4ce5a55@linaro.org> (raw)
Hi all,
Apologies I was meant to organize the call earlier.
I would suggest to have the next community call on Wednesday 22nd
November 5pm GMT. Does it sound good?
Do you have any specific topic you would like to discuss?
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2017-11-16 11:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 11:54 Julien Grall [this message]
2017-11-16 12:47 ` Next Xen Arm Community call - Wednesday 22nd November Artem Mygaiev
2017-11-16 18:58 ` Stefano Stabellini
2017-11-20 18:05 ` Julien Grall
2017-11-21 14:34 ` Julien Grall
2017-11-27 17:01 ` [RFC] WIP: optee: add OP-TEE mediator Volodymyr Babchuk
2017-12-01 22:58 ` Stefano Stabellini
2017-12-04 14:30 ` Julien Grall
2017-12-04 16:24 ` Volodymyr Babchuk
2017-12-04 16:29 ` Julien Grall
2017-12-06 22:39 ` Julien Grall
2017-12-04 14:46 ` Andrew Cooper
2017-12-04 16:15 ` Volodymyr Babchuk
2017-12-04 16:27 ` Julien Grall
2017-12-04 18:32 ` Volodymyr Babchuk
2017-12-04 22:04 ` Stefano Stabellini
2017-12-05 11:14 ` Julien Grall
[not found] ` <f9fe1cb6-8700-99ba-ee62-2217fb5eb041@linaro.org>
[not found] ` <20171204185929.GB30163@EPUAKYIW2556.kyiv.epam.com>
[not found] ` <a6a05ad8-f335-00a2-cdd0-add81deb87bf@linaro.org>
[not found] ` <2ee9297a-fcb8-c1c0-8ca7-91b9adbcd5b1@epam.com>
[not found] ` <a7af95e4-09cf-22f8-b8cd-23a0cb5baae8@linaro.org>
2017-12-05 15:36 ` Stuart Yoder
2017-12-06 22:31 ` Julien Grall
2017-12-07 16:32 ` Stuart Yoder
2017-12-04 22:06 ` Stefano Stabellini
2017-12-05 13:07 ` Volodymyr Babchuk
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=92b77e94-00ff-d81b-e4e0-bb7cf4ce5a55@linaro.org \
--to=julien.grall@linaro.org \
--cc=Artem_Mygaiev@epam.com \
--cc=Jarvis.Roach@dornerworks.com \
--cc=anastassios.nanos@onapp.com \
--cc=edgar.iglesias@xilinx.com \
--cc=lars.kurth@citrix.com \
--cc=scampbel@codeaurora.org \
--cc=sgoel@codeaurora.org \
--cc=sstabellini@kernel.org \
--cc=stewart.Hildebrand@dornerworks.com \
--cc=vfachin@de.adit-jv.com \
--cc=volodymyr_babchuk@epam.com \
--cc=xen-devel@lists.xenproject.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).