From: Luis Chamberlain <mcgrof@kernel.org>
To: Brendan Higgins <brendanhiggins@google.com>
Cc: Knut Omang <knut.omang@oracle.com>, shuah <shuah@kernel.org>,
KUnit Development <kunit-dev@googlegroups.com>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
Alan Maguire <alan.maguire@oracle.com>
Subject: Re: Plan for hybrid testing
Date: Sat, 19 Oct 2019 18:44:50 +0000 [thread overview]
Message-ID: <20191019184450.GH11244@42.do-not-panic.com> (raw)
In-Reply-To: <CAFd5g459xmO+=QPhnnXVO8+dB_t1PViXxK-Fz6Zp+sp5suJZ2w@mail.gmail.com>
On Fri, Oct 18, 2019 at 12:58:01PM -0700, Brendan Higgins wrote:
> On Fri, Oct 18, 2019 at 12:23 PM Luis Chamberlain <mcgrof@kernel.org> wrote:
> > >
> > > Do we really want to focus on this point now? I think it's better to
> > > start off with something simple and evolve it.
> >
> > Addressing it can help simplfiy things long term, as perhaps we really
> > don't need something like generic netlink to orchestrate.
>
> Sure, I just think it sounds like we don't need it for a lot of
> things, so if something significantly simpler exists, maybe we should
> just start there. But yeah, starting that discussion here and now
> doesn't hurt as long as we don't lose sight of something concrete in
> the short term.
>
> Cool, sounds like we are on the same page then.
Indeed.
Luis
next prev parent reply other threads:[~2019-10-19 18:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 21:02 Plan for hybrid testing Brendan Higgins
2019-09-16 16:20 ` shuah
2019-10-14 10:42 ` Luis Chamberlain
2019-10-14 18:38 ` Knut Omang
2019-10-14 19:01 ` shuah
2019-10-16 10:52 ` Knut Omang
2019-10-16 13:08 ` Luis Chamberlain
2019-10-17 17:46 ` Knut Omang
2019-10-17 19:11 ` shuah
2019-10-18 9:47 ` Luis Chamberlain
2019-10-18 18:35 ` Brendan Higgins
2019-10-18 19:22 ` Luis Chamberlain
2019-10-18 19:58 ` Brendan Higgins
2019-10-19 18:44 ` Luis Chamberlain [this message]
2019-10-18 21:42 ` shuah
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=20191019184450.GH11244@42.do-not-panic.com \
--to=mcgrof@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=brendanhiggins@google.com \
--cc=knut.omang@oracle.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.