From: Steven Rostedt <rostedt@goodmis.org>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
"Enrico Weigelt, metux IT consult" <lkml@metux.net>,
David Hildenbrand <david@redhat.com>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Greg KH <greg@kroah.com>, Christoph Lameter <cl@gentwo.de>,
Theodore Ts'o <tytso@mit.edu>, Jiri Kosina <jikos@kernel.org>,
ksummit@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, netdev@vger.kernel.org,
linux-arch@vger.kernel.org, linux-api@vger.kernel.org
Subject: Re: Maintainers / Kernel Summit 2021 planning kick-off
Date: Tue, 22 Jun 2021 20:15:34 -0400 [thread overview]
Message-ID: <20210622201534.53d3067b@rorschach.local.home> (raw)
In-Reply-To: <66fce207-2602-6452-9216-01ebde656bcd@linuxfoundation.org>
On Tue, 22 Jun 2021 17:57:11 -0600
Shuah Khan <skhan@linuxfoundation.org> wrote:
> Correct. It will be impossible to participate and moderate in workshop
> > setting. We have to ask for volunteers and nominate moderators ahead of
> > time.
> >
>
> Subsystems could seek volunteers from other subsystems perhaps ...
Right, this is exactly what I was thinking. I could moderate a GPU
subsystem, and even though I'm know for speaking, I would keep my mouth
shut for such a session, as I'm totally clueless when it comes to the
GPU subsystem ;-)
-- Steve
next prev parent reply other threads:[~2021-06-23 0:15 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 15:28 Maintainers / Kernel Summit 2021 planning kick-off Theodore Ts'o
2021-04-28 10:29 ` Jiri Kosina
2021-04-30 21:48 ` Theodore Ts'o
2021-05-27 13:23 ` Christoph Lameter
2021-05-27 13:29 ` Greg KH
2021-05-28 14:58 ` James Bottomley
2021-05-28 15:11 ` Matthew Wilcox
2021-05-28 15:27 ` James Bottomley
2021-05-28 15:31 ` Laurent Pinchart
2021-05-28 15:44 ` James Bottomley
2021-05-28 15:55 ` Laurent Pinchart
2021-05-28 16:04 ` James Bottomley
2021-05-28 16:31 ` Laurent Pinchart
2021-05-28 15:42 ` Toke Høiland-Jørgensen
2021-06-09 10:37 ` David Hildenbrand
2021-06-09 19:23 ` James Bottomley
2021-06-11 10:58 ` Enrico Weigelt, metux IT consult
2021-06-10 18:07 ` Enrico Weigelt, metux IT consult
2021-06-10 18:23 ` Konstantin Ryabitsev
2021-06-10 18:39 ` Laurent Pinchart
2021-06-10 19:26 ` Steven Rostedt
2021-06-10 19:55 ` Shuah Khan
2021-06-10 20:02 ` Steven Rostedt
2021-06-10 20:20 ` Matthew Wilcox
2021-06-10 20:31 ` Steven Rostedt
2021-06-10 22:43 ` Toke Høiland-Jørgensen
2021-06-11 2:59 ` Willy Tarreau
2021-06-11 9:13 ` Mauro Carvalho Chehab
2021-06-11 9:51 ` Willy Tarreau
2021-06-18 13:46 ` Laurent Pinchart
2021-06-18 14:11 ` James Bottomley
2021-06-18 14:17 ` Steven Rostedt
2021-06-18 14:28 ` Geert Uytterhoeven
2021-06-18 14:32 ` Steven Rostedt
2021-06-18 14:45 ` Laurent Pinchart
2021-06-18 14:58 ` Geert Uytterhoeven
2021-06-18 15:14 ` Matthew Wilcox
2021-06-18 15:23 ` Steven Rostedt
2021-06-18 15:29 ` Geert Uytterhoeven
2021-06-18 15:34 ` Steven Rostedt
2021-06-18 15:36 ` Steven Rostedt
2021-06-18 16:33 ` Mauro Carvalho Chehab
2021-06-18 15:58 ` Mark Brown
2021-06-18 16:45 ` Mauro Carvalho Chehab
2021-06-18 14:46 ` James Bottomley
2021-06-22 22:33 ` Shuah Khan
2021-06-22 22:59 ` Laurent Pinchart
2021-06-22 23:33 ` Shuah Khan
2021-06-22 23:57 ` Shuah Khan
2021-06-23 0:06 ` Laurent Pinchart
2021-06-23 0:15 ` Steven Rostedt [this message]
2021-06-10 20:12 ` Konstantin Ryabitsev
2021-06-10 18:55 ` Linus Torvalds
2021-06-18 13:34 ` Enrico Weigelt, metux IT consult
2021-06-18 14:08 ` Steven Rostedt
2021-06-11 11:10 ` David Howells
2021-06-15 18:23 ` Enrico Weigelt, metux IT consult
2021-06-15 18:30 ` Matthew Wilcox
2021-06-15 18:34 ` Konstantin Ryabitsev
2021-06-15 18:40 ` Laurent Pinchart
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=20210622201534.53d3067b@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=cl@gentwo.de \
--cc=david@redhat.com \
--cc=greg@kroah.com \
--cc=jikos@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=ksummit@lists.linux.dev \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkml@metux.net \
--cc=netdev@vger.kernel.org \
--cc=skhan@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 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.