ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
* Re: [Ksummit-discuss] Scheduling 2nd slot for Compute-Offload devices for 3:30pm?
@ 2015-10-27  4:01 Jörg Rödel
  0 siblings, 0 replies; 2+ messages in thread
From: Jörg Rödel @ 2015-10-27  4:01 UTC (permalink / raw)
  To: Theodore Ts'o; +Cc: ksummit-discuss

[-- 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 --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [Ksummit-discuss] Scheduling 2nd slot for Compute-Offload devices for 3:30pm?
@ 2015-10-27  2:41 Theodore Ts'o
  0 siblings, 0 replies; 2+ messages in thread
From: Theodore Ts'o @ 2015-10-27  2:41 UTC (permalink / raw)
  To: Joerg Roedel; +Cc: ksummit-discuss

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
							

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2015-10-27  4:01 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-10-27  4:01 [Ksummit-discuss] Scheduling 2nd slot for Compute-Offload devices for 3:30pm? Jörg Rödel
  -- strict thread matches above, loose matches on Subject: below --
2015-10-27  2:41 Theodore Ts'o

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox