From: Theodore Ts'o <tytso@mit.edu>
To: Joerg Roedel <joro@8bytes.org>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] Scheduling 2nd slot for Compute-Offload devices for 3:30pm?
Date: Mon, 26 Oct 2015 22:41:11 -0400 [thread overview]
Message-ID: <20151027024111.GA7701@thunk.org> (raw)
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
next reply other threads:[~2015-10-27 2:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 2:41 Theodore Ts'o [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-10-27 4:01 [Ksummit-discuss] Scheduling 2nd slot for Compute-Offload devices for 3:30pm? Jörg Rödel
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=20151027024111.GA7701@thunk.org \
--to=tytso@mit.edu \
--cc=joro@8bytes.org \
--cc=ksummit-discuss@lists.linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.