From: Thomas Gleixner <tglx@linutronix.de>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] Draft Kernel Summit track agenda
Date: Wed, 7 Nov 2018 22:05:55 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.21.1811072204520.1666@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20181107174720.GA6135@thunk.org>
Ted,
On Wed, 7 Nov 2018, Theodore Y. Ts'o wrote:
> Here is an initial draft agenda for the Kernel Summit track. I did my
> best to avoid potential schedule conflicts, but I'm sure I didn't
> quite get things completely right. Please let me know if you spot any
> problems with conflicts with LPC microconfs or other LPC tracks.
I didn't spot any obvious ones. That must have been quite some juggling.
Thanks,
Thomas
next prev parent reply other threads:[~2018-11-07 21:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 17:47 Theodore Y. Ts'o
2018-11-07 21:05 ` Thomas Gleixner [this message]
2018-11-07 21:53 ` Theodore Y. Ts'o
2018-11-08 10:06 ` Greg KH
2018-11-08 12:28 ` Boaz Harrosh
2018-11-08 15:40 ` Greg KH
2018-11-08 16:05 ` Theodore Y. Ts'o
2018-11-08 17:31 ` Boaz Harrosh
2018-11-08 18:05 ` Matthew Wilcox
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=alpine.DEB.2.21.1811072204520.1666@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--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