From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: "Theodore Ts'o" <tytso@mit.edu>,
ksummit-discuss@lists.linux-foundation.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Alex Deucher <alexdeucher@gmail.com>,
Sean Paul <seanpaul@chromium.org>,
"Nikula, Jani" <jani.nikula@linux.intel.com>
Subject: Re: [Ksummit-discuss] Next steps and plans for the 2017 Maintainer and Kernel Summits
Date: Tue, 27 Jun 2017 15:23:01 +0200 [thread overview]
Message-ID: <CAKMK7uHM8FN1EuQi-fFdwbphud+7krjdbvkFfoK84r-zAae1qw@mail.gmail.com> (raw)
In-Reply-To: <20170614132920.csogpzkl4k5k7kaj@thunk.org>
On Wed, Jun 14, 2017 at 3:29 PM, Theodore Ts'o <tytso@mit.edu> wrote:
> Daniel Vetter
So I've completely screwed up travel planning (well properly checking
my calendar back when we discuss this a while back) and I can't attend
ks :-/
We discussed this among drm maintainers and we'd like to volunteer
Sean Paul as drm rep. He's done drm-misc maintainer (so knows drm core
stuff, and drm-misc is run with the committer model too), and he could
also bring in the drm consumer pov being on google's cros team. Jani
would be another option, but he's busy building a house then, Alex
would be another (he's been around as maintainer forever, at least
longer than me), but Dave thinks Sean would be better fit for
representing drm overall at ks.
Cheers, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
prev parent reply other threads:[~2017-06-27 13:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 13:29 Theodore Ts'o
2017-06-21 5:04 ` Theodore Ts'o
2017-06-27 13:23 ` Daniel Vetter [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=CAKMK7uHM8FN1EuQi-fFdwbphud+7krjdbvkFfoK84r-zAae1qw@mail.gmail.com \
--to=daniel.vetter@ffwll.ch \
--cc=alexdeucher@gmail.com \
--cc=jani.nikula@linux.intel.com \
--cc=ksummit-discuss@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanpaul@chromium.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