workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Brauner <christian.brauner@ubuntu.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Dmitry Vyukov <dvyukov@google.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	Dmitry Vyukov <dvyukov@gmail.com>, Theodore Ts'o <tytso@mit.edu>,
	Rob Herring <robh@kernel.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	workflows@vger.kernel.org, Shuah Khan <skhan@linuxfoundation.org>,
	Bjorn Helgaas <helgaas@kernel.org>,
	Jiri Kosina <jikos@kernel.org>,
	Jani Nikula <jani.nikula@intel.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	stefan@datenfreihafen.org, Sasha Levin <sashal@kernel.org>,
	Christoph Hellwig <hch@lst.de>,
	David Miller <davem@davemloft.net>,
	Christian Brauner <christian@brauner.io>
Subject: Re: [MAINTAINERS SUMMIT] Reflections on kernel development processes
Date: Fri, 11 Oct 2019 15:19:18 +0200	[thread overview]
Message-ID: <20191011131917.mkq3n5332xlf6lhy@wittgenstein> (raw)
In-Reply-To: <20191011091812.68257184@gandalf.local.home>

On Fri, Oct 11, 2019 at 09:18:12AM -0400, Steven Rostedt wrote:
> On Fri, 11 Oct 2019 11:33:35 +0200
> Dmitry Vyukov <dvyukov@google.com> wrote:
> 
> > > Let's try to figure out time then.
> > > I propose the first day to not leave it to the last day and we may
> > > need some follow up discussions.
> > > On Monday I see Greg's keynote at 09:50 - 10:10. Steven's talk at
> > > 12:20 - 12:55. Sasha's talk at 12:20 - 12:55. Any other conflicts for
> > > people who want to attend?
> > > What about 10:30-11:30 (this covers a coffee break at 10:45-11:00, can
> > > prolong it to 12:00)? Any other time slot proposals?  
> > 
> > +Christian also expressed interest, his talks are 14:25 - 15:50 and
> > 16:20 - 16:55 on Monday.
> 
> If everyone's giving a talk on Monday, can we do this meeting on
> Tuesday?
> 
> It's much easier to concentrate if you don't have to worry about a talk
> you are about to give (or just finished).

Seconded. :)

Christian

  reply	other threads:[~2019-10-11 13:19 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190912120602.GC29277@pure.paranoia.local>
2019-09-22 12:02 ` [Ksummit-discuss] [MAINTAINERS SUMMIT] Reflections on kernel development processes Dmitry Vyukov
2019-09-23 12:52   ` Daniel Borkmann
2019-09-23 14:08     ` Dmitry Vyukov
2019-09-23 14:57       ` Daniel Borkmann
2019-09-30 21:24     ` Konstantin Ryabitsev
2019-10-01 21:33       ` Daniel Borkmann
2019-10-02 15:04         ` Konstantin Ryabitsev
2019-09-30 20:24   ` Konstantin Ryabitsev
2019-10-08  6:46     ` Dmitry Vyukov
2019-10-08 16:51       ` Konstantin Ryabitsev
2019-10-11  2:16         ` Konstantin Ryabitsev
2019-10-11  2:30           ` Steven Rostedt
2019-10-11  8:30           ` Greg Kroah-Hartman
2019-10-11  8:59             ` Dmitry Vyukov
2019-10-11  9:33               ` Dmitry Vyukov
2019-10-11  9:40                 ` Christian Brauner
2019-10-11 13:18                 ` Steven Rostedt
2019-10-11 13:19                   ` Christian Brauner [this message]
2019-10-11 13:30                     ` Dmitry Vyukov
2019-10-11 13:40                       ` Laurent Pinchart
2019-10-11 15:28                       ` Jonathan Corbet
2019-10-14  7:42                       ` Nicolas Belouin
2019-10-14  7:52                         ` Daniel Vetter
2019-10-15  7:31                           ` Dmitry Vyukov
2019-10-15 16:17                             ` Konstantin Ryabitsev
2019-10-11 10:46           ` Dmitry Vyukov
2019-10-11 13:29           ` Laurent Pinchart
2019-10-11 13:51             ` Theodore Y. Ts'o

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=20191011131917.mkq3n5332xlf6lhy@wittgenstein \
    --to=christian.brauner@ubuntu.com \
    --cc=christian@brauner.io \
    --cc=davem@davemloft.net \
    --cc=dvyukov@gmail.com \
    --cc=dvyukov@google.com \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=helgaas@kernel.org \
    --cc=jani.nikula@intel.com \
    --cc=jikos@kernel.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=rjw@rjwysocki.net \
    --cc=robh@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=sashal@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=stefan@datenfreihafen.org \
    --cc=tytso@mit.edu \
    --cc=workflows@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).