From: Michael Ellerman <mpe@ellerman.id.au>
To: Guenter Roeck <linux@roeck-us.net>, "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] new topic: regression test infrastructure? (was Draft Maintainer's Summit Agenda and Attendees - )
Date: Wed, 17 Oct 2018 11:08:47 +1100 [thread overview]
Message-ID: <87a7ndl9io.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20181016211446.GA28549@roeck-us.net>
Guenter Roeck <linux@roeck-us.net> writes:
> On Tue, Oct 16, 2018 at 04:51:09PM -0400, Theodore Y. Ts'o wrote:
>> On Tue, Oct 16, 2018 at 09:53:06PM +0200, Christian Borntraeger wrote:
>> >
>> > On 10/16/2018 04:12 AM, Theodore Y. Ts'o wrote:
>> > > This is the draft agenda for the Maintainer's Summit which I and the
>> > > program committee have come up with:
>> > > [..]
>> > > 2:30 TBD
>> > > [..]
>> > > 4:30 TBD
>> >
>> > Does it make sense to talk about existing test infrastructure
>> > (like syzbot,Geert Uytterhoeven and Guenter Roecks reports as well as all the others)
>> > What architectures are missing? Is it ok to run tests in-house and only report errors?
>> > What test scenarios are missing?
>>
>> This would probably be better suited at the Kernel Summit track in
>> Vancouver next month, as there will be a much larger number of kernel
>> developers there. The Maintainer's Summit is intended to focus much
>> more process issues than specific technical questions.
>>
>
> In Edinburgh: https://elinux.org/Automated_Testing_Summit
Oh cool, first I've heard of it.
Mind if I drop in? :)
cheers
next prev parent reply other threads:[~2018-10-17 0:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 2:12 [Ksummit-discuss] Draft Maintainer's Summit Agenda and Attendees Theodore Y. Ts'o
2018-10-16 8:11 ` Daniel Vetter
2018-10-16 15:13 ` James Bottomley
2018-10-16 18:00 ` Josh Triplett
2018-10-16 18:19 ` James Bottomley
2018-10-16 18:38 ` Tim.Bird
2018-10-16 18:46 ` Josh Triplett
2018-10-16 18:57 ` Daniel Vetter
2018-10-16 18:52 ` James Bottomley
2018-10-16 18:16 ` Mark Brown
2018-10-16 18:36 ` Chris Mason
2018-10-16 19:53 ` [Ksummit-discuss] new topic: regression test infrastructure? (was Draft Maintainer's Summit Agenda and Attendees - ) Christian Borntraeger
2018-10-16 20:51 ` Theodore Y. Ts'o
2018-10-16 21:11 ` Jiri Kosina
2018-10-16 21:14 ` Guenter Roeck
2018-10-16 21:46 ` Theodore Y. Ts'o
2018-10-17 0:08 ` Michael Ellerman [this message]
2018-10-17 1:06 ` Tim.Bird
2018-10-17 1:51 ` Shuah Khan
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=87a7ndl9io.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux@roeck-us.net \
--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