From: Theodore Ts'o <tytso@mit.edu>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Kirill Kolyshkin <kir@openvz.org>,
Andrei Vagin <avagin@openvz.org>,
ksummit-discuss@lists.linuxfoundation.org,
Eric Dumazet <edumazet@google.com>,
David Ahern <dsahern@gmail.com>,
Patrick McHardy <kaber@trash.net>,
Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Netlink engine issues, and ways to fix those
Date: Tue, 1 Nov 2016 12:39:14 -0400 [thread overview]
Message-ID: <20161101163914.o4uyvkgk2n6t2ncb@thunk.org> (raw)
In-Reply-To: <1478012335.2972.9.camel@HansenPartnership.com>
On Tue, Nov 01, 2016 at 08:58:55AM -0600, James Bottomley wrote:
> The Kernel Summit plenary track is also accepting submissions here:
>
> https://linuxplumbersconf.org/2016/ocw/events/KS2016/proposals
>
> The KS track has the Coronado room from Tuesday-Friday (ending around
> 14:00 on Friday), so you can work out your best time to schedule this.
> Ted (as KS chair) makes the final decision, so it's a good idea as
> well as submitting the proposal to send email here so Ted can gauge how
> much interest there is for the proposal.
More than good idea; *please* send a proposal to this list, along with
your preferences of when the session should scheduled, so the critical
participants for your sessions don't have conflicts with the other LPC
events.
If you make the presentation using the web link above, it means you'll
be able to edit the description after we approve it, and it will be
reflected on the schedule. Otherwise I will make the submission on
your behalf, which might be more convenient for you, but the tradeoff
is that you won't be able to edit abstract afterwards.
- Ted
next prev parent reply other threads:[~2016-11-01 16:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-03 5:20 Andrei Vagin
2016-09-04 19:03 ` Andy Lutomirski
2016-09-05 19:30 ` Alexei Starovoitov
2016-09-06 16:05 ` Stephen Hemminger
2016-09-12 14:05 ` Hannes Reinecke
2016-09-13 17:29 ` Eric W. Biederman
2016-09-16 5:58 ` Andrei Vagin
2016-09-18 20:18 ` Eric W. Biederman
2016-10-11 2:13 ` Andrei Vagin
2016-10-11 14:14 ` Alexey Dobriyan
2016-11-01 3:15 ` Andrei Vagin
2016-11-01 14:58 ` James Bottomley
2016-11-01 16:39 ` Theodore Ts'o [this message]
[not found] ` <CANaxB-ycZFtZW3=WasEDXgBwf3NF4C46aNwTOpKqHjuPbN5e-Q@mail.gmail.com>
2016-11-03 15:41 ` Andrey Vagin
2016-11-03 21:04 Kirill Kolyshkin
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=20161101163914.o4uyvkgk2n6t2ncb@thunk.org \
--to=tytso@mit.edu \
--cc=James.Bottomley@HansenPartnership.com \
--cc=avagin@openvz.org \
--cc=dsahern@gmail.com \
--cc=edumazet@google.com \
--cc=kaber@trash.net \
--cc=kir@openvz.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=pablo@netfilter.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