[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACT4Y+aq0eu5gG=Xnc6nDkQoH+_Hh=q3iiivq4nOowG8ncG+Cw@mail.gmail.com>
Date: Wed, 22 May 2019 18:04:05 +0200
From: Dmitry Vyukov <dvyukov@...gle.com>
To: Tim Bird <Tim.Bird@...y.com>
Cc: sashal@...nel.org, Tim Bird <tbird20d@...il.com>,
Veronika Kabatova <vkabatov@...hat.com>,
Dhaval Giani <dhaval.giani@...il.com>,
Sasha Levin <alexander.levin@...rosoft.com>,
Shuah Khan <shuah@...nel.org>,
Kevin Hilman <khilman@...libre.com>,
LKML <linux-kernel@...r.kernel.org>,
Steven Rostedt <rostedt@...dmis.org>,
Dan Carpenter <dan.carpenter@...cle.com>,
Matthew Wilcox <willy@...radead.org>,
gustavo padovan <gustavo.padovan@...labora.co.uk>,
knut omang <knut.omang@...cle.com>,
Eliska Slobodova <eslobodo@...hat.com>
Subject: Re: Linux Testing Microconference at LPC
On Thu, May 16, 2019 at 2:51 AM <Tim.Bird@...y.com> wrote:
> > -----Original Message-----
> > From: Sasha Levin
> >
> > On Fri, Apr 26, 2019 at 02:02:53PM -0700, Tim Bird wrote:
> ...
> > >
> > >With regards to the Testing microconference at Plumbers, I would like
> > >to do a presentation on the current status of test standards and test
> > >framework interoperability. We recently had some good meetings
> > >between the LAVA and Fuego people at Linaro Connect
> > >on this topic.
> >
> > Hi Tim,
> >
> > Sorry for the delayed response, this mail got marked as read as a result
> > of fat fingers :(
> >
> > I'd want to avoid having an 'overview' talk as part of the MC. We have
> > quite a few discussion topics this year and in the spirit of LPC I'd
> > prefer to avoid presentations.
>
> OK. Sounds good.
>
> > Maybe it's more appropriate for the refereed track?
> I'll consider submitting it there, but there's a certain "fun" aspect
> to attending a conference that I don't have to prepare a talk for. :-)
>
> Thanks for getting back to me. I'm already registered for Plumbers,
> so I'll see you there.
> -- Tim
I would like to give an update on syzkaller/syzbot and discuss:
- testability of kernel components in this context
- test coverage and what's still not tested
- discussion of the process (again): what works, what doesn't work, feedback
I also submitted a refereed track talk called "Reflections on kernel
quality, development process and testing". If it's not accepted, I
would like to do it on Testing MC.
Powered by blists - more mailing lists