From: Jiri Kosina <jikos@kernel.org>
To: "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: Tue, 16 Oct 2018 23:11:17 +0200 (CEST) [thread overview]
Message-ID: <nycvar.YFH.7.76.1810162308110.23511@cbobk.fhfr.pm> (raw)
In-Reply-To: <20181016205109.GB14947@thunk.org>
On Tue, 16 Oct 2018, Theodore Y. Ts'o wrote:
> 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.
At least for SUSE I can say is that we're going to have a decent
representation on LPC/KS in Vancouver, and we are one of those who do
support power and Z series for (part of) living, so this could eventually
be a useful discussion (especially in case other vendors on the same boat
are represented there as well).
Thanks,
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2018-10-16 21:11 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 [this message]
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=nycvar.YFH.7.76.1810162308110.23511@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=ksummit-discuss@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox