From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Andrei Vagin <avagin@openvz.org>,
ksummit-discuss@lists.linuxfoundation.org
Cc: Kirill Kolyshkin <kir@openvz.org>,
Eric Dumazet <edumazet@google.com>,
Patrick McHardy <kaber@trash.net>,
Pablo Neira Ayuso <pablo@netfilter.org>,
David Ahern <dsahern@gmail.com>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Netlink engine issues, and ways to fix those
Date: Tue, 01 Nov 2016 08:58:55 -0600 [thread overview]
Message-ID: <1478012335.2972.9.camel@HansenPartnership.com> (raw)
In-Reply-To: <20161101031506.GA32626@outlook.office365.com>
On Mon, 2016-10-31 at 20:15 -0700, Andrei Vagin wrote:
> Hello everyone,
>
> I have never been before on kernel-summit and don't know how talks
> are planed here. Looks like we have enough people how want to duscuss
> the subject. Maybe, if it is not too late, we can choose a time for
> this discussion?
>
> I'm here for Linux Plumbers and have a definite plan on Friday from
> 2pm to 5pm. Any other time works for me.
I suppose the process is a bit nebulous, let me try to explain it.
Plumbers and the Kernel Summit open track are running in parallel.
Plumbers has room for BoFs if you want to submit one:
https://linuxplumbersconf.org/2016/ocw/events/LPC2016BOFS/proposals
They'll be scheduled on Thursday evening. You could also try to get it
into a relevant MC, but you have to negotiate that with the person
running the MC.
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.
James
next prev parent reply other threads:[~2016-11-01 14:58 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 [this message]
2016-11-01 16:39 ` Theodore Ts'o
[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=1478012335.2972.9.camel@HansenPartnership.com \
--to=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