From: Juri Lelli <juri.lelli@redhat.com>
To: linux-pm@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-pci@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: [ANNOUNCE] OSPM-summit 2018 - live events
Date: Fri, 13 Apr 2018 18:42:41 +0200 [thread overview]
Message-ID: <20180413164241.GB10485@localhost.localdomain> (raw)
Hi all,
Gentle reminder that the Power Management and Scheduling in the Linux
Kernel II edition summit (OSPM-summit 2018) is happening next week.
April 16-18, 2018
Scuola Superiore Sant'Anna
Pisa, Italy
http://retis.sssup.it/ospm-summit/
If you didn't make it this year, but you are still interested in what is
going to be discussed there, good news is that all the talks are going
to be streamed online and recorded. Please find schedule and links to
the live events at:
http://retis.sssup.it/ospm-summit/program.html
If you wish to participate remotely, simply send me a private email
specifying which Google Hangouts contact I should be inviting to join
the live event (it worked great last year! :).
Best,
- Juri
reply other threads:[~2018-04-13 16:42 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=20180413164241.GB10485@localhost.localdomain \
--to=juri.lelli@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.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