linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: "Gustavo Padovan" <gustavo.padovan@collabora.com>
Cc: "Dhaval Giani" <dhaval.giani@gmail.com>,
	"Sasha Levin" <alexander.levin@microsoft.com>,
	"shuah" <shuah@kernel.org>, "Kevin Hilman" <khilman@baylibre.com>,
	"Tim Bird" <tbird20d@gmail.com>,
	"LKML" <linux-kernel@vger.kernel.org>,
	"Carpenter,Dan" <dan.carpenter@oracle.com>,
	willy@infradead.org, "Dmitry Vyukov" <dvyukov@google.com>,
	knut.omang@oracle.com,
	"Guillaume Charles Tucker" <guillaume.tucker@collabora.com>
Subject: Re: Linux Testing Microconference at LPC
Date: Thu, 18 Apr 2019 09:26:24 -0400	[thread overview]
Message-ID: <20190418092624.61b3611b@gandalf.local.home> (raw)
In-Reply-To: <2dfb-5cb85000-7-65937800@86141034>

On Thu, 18 Apr 2019 11:22:47 +0100
"Gustavo Padovan" <gustavo.padovan@collabora.com> wrote:

> Guillaume would like to talk about the his work on kernelCI on automated bisection, functional testing and modular pipelines.

Can you be more specific about what Guillaume wants to talk about for
those topics? I hope it's not just a "let everyone know what Guillaume
has done" talk. Plumbers is about discussions of on going and future
work. If these are all work-in-progress and Guillaume is looking for
input from other stakeholder developers, then that is exactly what
Plumbers is about. But if this is just to show developers what was done
and how to use the finished work, then save that for something like
Open Source Summit.

-- Steve

  reply	other threads:[~2019-04-18 13:26 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-11 17:37 Linux Testing Microconference at LPC Dhaval Giani
2019-04-18 10:22 ` Gustavo Padovan
2019-04-18 13:26   ` Steven Rostedt [this message]
2019-04-22  7:12     ` Guillaume Tucker
2019-04-23  8:37 ` Knut Omang
2019-04-23 10:22 ` Mark Rutland
2019-05-12  0:40   ` Andrea Parri
2019-05-22 15:52     ` Dmitry Vyukov
2019-05-23 14:03       ` Paul E. McKenney
2019-04-25 13:37 ` Veronika Kabatova
2019-04-26 21:02   ` Tim Bird
2019-05-16  0:39     ` Sasha Levin
2019-05-16  0:51       ` Tim.Bird
2019-05-22 16:04         ` Dmitry Vyukov
2019-05-22 16:07           ` Dhaval Giani
2019-05-22 15:48     ` Dmitry Vyukov
2019-05-23  0:07       ` Tim.Bird
2019-05-23  6:49         ` Dmitry Vyukov
2019-05-15 22:44 ` shuah
2019-05-15 23:19   ` Brendan Higgins
2019-05-16  0:36   ` Sasha Levin
2019-05-22 21:02     ` Brendan Higgins
2019-05-23  0:58       ` Steven Rostedt
2019-05-23  1:00         ` Steven Rostedt
2019-05-23  4:54       ` Knut Omang
2019-06-03  8:59         ` Brendan Higgins
2019-05-22 16:11 ` Dhaval Giani
2019-06-10 11:21   ` Douglas Raillard

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=20190418092624.61b3611b@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=alexander.levin@microsoft.com \
    --cc=dan.carpenter@oracle.com \
    --cc=dhaval.giani@gmail.com \
    --cc=dvyukov@google.com \
    --cc=guillaume.tucker@collabora.com \
    --cc=gustavo.padovan@collabora.com \
    --cc=khilman@baylibre.com \
    --cc=knut.omang@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=tbird20d@gmail.com \
    --cc=willy@infradead.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).