From: "Jörg Rödel" <joro@8bytes.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] Scheduling 2nd slot for Compute-Offload devices for 3:30pm?
Date: Tue, 27 Oct 2015 13:01:30 +0900 [thread overview]
Message-ID: <nj48vhqn8l0cinev4orm7ljd.1445918490599@email.android.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 587 bytes --]
Works for me, thanks for setting it up!
Sent from a Galaxy Class Phone
-------- Ursprüngliche Nachricht --------
Von: Theodore Ts'o <tytso@mit.edu>
Datum: 27.10.2015 11:41 (GMT+09:00)
An: Joerg Roedel <joro@8bytes.org>
Cc: ksummit-discuss@lists.linuxfoundation.org
Betreff: Scheduling 2nd slot for Compute-Offload devices for 3:30pm?
I have received a request to shcedule the 2nd slot of the Core Kernel
support for Compute-Offlad devices to 3:30pm instead of 3:00 to avoid
conflicting with the Improving Kernel Security sessions.
Any objections?
- Ted
[-- Attachment #2: Type: text/html, Size: 888 bytes --]
next reply other threads:[~2015-10-27 4:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 4:01 Jörg Rödel [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-10-27 2:41 Theodore Ts'o
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=nj48vhqn8l0cinev4orm7ljd.1445918490599@email.android.com \
--to=joro@8bytes.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=tytso@mit.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