From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Serge E. Hallyn" <serge@hallyn.com>, Theodore Ts'o <tytso@mit.edu>
Cc: "Tycho Andersen" <tycho.andersen@canonical.com>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>,
"Peter Zijlstra" <peterz@infradead.org>,
"Christian Brauner" <christian.brauner@mailbox.org>,
"Tejun Heo" <tj@kernel.org>,
"Stéphane Graber" <stgraber@ubuntu.com>
Subject: Re: [Ksummit-discuss] [LAST-MINUTE TOPIC] cgroup API
Date: Mon, 31 Oct 2016 09:28:50 -0600 [thread overview]
Message-ID: <1477927730.2981.1.camel@HansenPartnership.com> (raw)
In-Reply-To: <20161031150451.GA7383@mail.hallyn.com>
On Mon, 2016-10-31 at 10:04 -0500, Serge E. Hallyn wrote:
> On Sun, Oct 30, 2016 at 07:41:11PM -0400, Theodore Ts'o wrote:
> > On Sun, Oct 30, 2016 at 10:27:23AM -0500, Serge E. Hallyn wrote:
> > >
> > > FWIW I'm only arriving tuesday morning; but obviously far more
> > > important
> > > that Tejun be there, so I think I vote for monday night.
> >
> > we have time Monday *afternoon*, if that works for folks. Monday
> > evening will conflict with the evening dinner, so if we want to do
> > it
> > on Monday, we have free slots during the kernel summit core day.
> > If
> > there are people who need to attend who aren't core day invitees,
> > we
> > have invited people who are needed for a particular discussion into
> > a
> > specific core plenary day session before.
> >
> > The other alternative would be to either do it Tuesday (we have a
> > room
> > availble), or Wednesday or Thursday, where the kernel summit does
> > have
> > a room reserved for technical sessions and for which LPC attendees
> > are
> > explicitly invited (just as people with Kernel Summit badges are
> > invited to participate in LPC events).
> >
> > I note there is a Cgroup v2 API session scheduled as part of the
> > containers miniconference on Wednesday morning. I assume the goal
> > is
> > try to settle this disagreement before the LPC minisummit?
> >
> > Can someone give a summary of who the critical people are who need
> > to
> > be present, and what their availability might be? Finding a room
> > shouldn't be a problem. It's going to people's availability....
>
> Looks like
> Tejun obviously needs to be there
He's here all week, according to Chris.
> Andy wants to be there, and I assume it relates to his code
> There's an LXC contingency arriving monday night; I'd like
> someone (Christian, Stéphane, or Tycho) to make it on Tuesday
> if possible.
> I'd like to be there, but I arrive at 10:30 Tuesday morning.
> I don't think Eric Biederman is going to be in Santa Fe, but
> he'd be good to have there.
He's here now.
> I assume James Bottomley would like to be there?
Yes. (Provided you don't schedule it over anything I've said I'd go to,
which is why I like Tuesday). I've got something 09:30 on Tuesday, so
late morning or afternoon works.
James
> (I assume there are others, but that's the list I'm aware of)
> _______________________________________________
> Ksummit-discuss mailing list
> Ksummit-discuss@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
>
prev parent reply other threads:[~2016-10-31 15:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 17:29 [Ksummit-discuss] [LAST-MINUTE TOPIC] cgroup API Andy Lutomirski
2016-10-27 17:39 ` James Bottomley
2016-10-27 17:45 ` Josh Triplett
2016-10-27 20:09 ` Tejun Heo
2016-10-27 20:11 ` Paul Turner
2016-10-27 21:13 ` Peter Zijlstra
2016-10-30 23:50 ` Theodore Ts'o
2016-10-31 17:41 ` Rik van Riel
2016-10-30 15:27 ` Serge E. Hallyn
2016-10-30 23:41 ` Theodore Ts'o
2016-10-31 3:39 ` James Bottomley
2016-10-31 15:04 ` Serge E. Hallyn
2016-10-31 15:19 ` Tejun Heo
2016-10-31 17:06 ` Theodore Ts'o
2016-10-31 17:33 ` Tejun Heo
2016-10-31 17:35 ` James Bottomley
2016-11-01 13:33 ` James Bottomley
2016-10-31 17:40 ` Serge E. Hallyn
2016-10-31 17:42 ` Stéphane Graber
2016-10-31 23:00 ` Christian Brauner
2016-10-31 15:28 ` James Bottomley [this message]
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=1477927730.2981.1.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=christian.brauner@mailbox.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=peterz@infradead.org \
--cc=serge@hallyn.com \
--cc=stgraber@ubuntu.com \
--cc=tj@kernel.org \
--cc=tycho.andersen@canonical.com \
--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 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.