From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] new topic: regression test infrastructure? (was Draft Maintainer's Summit Agenda and Attendees - )
Date: Tue, 16 Oct 2018 16:51:09 -0400 [thread overview]
Message-ID: <20181016205109.GB14947@thunk.org> (raw)
In-Reply-To: <3af0bf1d-6dea-2736-b4f0-171db8a2d447@de.ibm.com>
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.
Also, some of these questions are best answered by those who can bring
resources to the table. For example, it's easy for someone to point
out that some architecture, like Itanium or pa-risc are "missing".
But the people to whom we would need to be having that conversation
would be Intel and HP, respectively, and both would likely say that
those architectures are obscelent, and so they would probably decline
to provide those resources.
Similarly, the question of whether, say, Power, or Z series, or Risc-V
are "missing" are best targetted at the companies which back those
architectures.
- Ted
next prev parent reply other threads:[~2018-10-16 20:51 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 [this message]
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
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=20181016205109.GB14947@thunk.org \
--to=tytso@mit.edu \
--cc=borntraeger@de.ibm.com \
--cc=ksummit-discuss@lists.linuxfoundation.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