From: shuah <shuah@kernel.org>
To: Dhaval Giani <dhaval.giani@gmail.com>,
Sasha Levin <alexander.levin@microsoft.com>,
Kevin Hilman <khilman@baylibre.com>,
Tim Bird <tbird20d@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Brendan Higgins <brendanhiggins@google.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
"Carpenter,Dan" <dan.carpenter@oracle.com>,
willy@infradead.org, gustavo.padovan@collabora.co.uk,
Dmitry Vyukov <dvyukov@google.com>,
knut.omang@oracle.com, shuah <shuah@kernel.org>
Subject: Re: Linux Testing Microconference at LPC
Date: Wed, 15 May 2019 16:44:19 -0600 [thread overview]
Message-ID: <3c6c9405-7e90-fb03-aa1c-0ada13203980@kernel.org> (raw)
In-Reply-To: <CAPhKKr_uVTFAzne0QkZFUGfb8RxQdVFx41G9kXRY7sFN-=pZ6w@mail.gmail.com>
Hi Sasha and Dhaval,
On 4/11/19 11:37 AM, Dhaval Giani wrote:
> Hi Folks,
>
> This is a call for participation for the Linux Testing microconference
> at LPC this year.
>
> For those who were at LPC last year, as the closing panel mentioned,
> testing is probably the next big push needed to improve quality. From
> getting more selftests in, to regression testing to ensure we don't
> break realtime as more of PREEMPT_RT comes in, to more stable distros,
> we need more testing around the kernel.
>
> We have talked about different efforts around testing, such as fuzzing
> (using syzkaller and trinity), automating fuzzing with syzbot, 0day
> testing, test frameworks such as ktests, smatch to find bugs in the
> past. We want to push this discussion further this year and are
> interested in hearing from you what you want to talk about, and where
> kernel testing needs to go next.
>
> Please let us know what topics you believe should be a part of the
> micro conference this year.
>
> Thanks!
> Sasha and Dhaval
>
A talk on KUnit from Brendan Higgins will be good addition to this
Micro-conference. I am cc'ing Brendan on this thread.
Please consider adding it.
thanks,
-- Shuah
next prev parent reply other threads:[~2019-05-15 22:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 17:37 Dhaval Giani
2019-04-18 10:22 ` Gustavo Padovan
2019-04-18 13:26 ` Steven Rostedt
2019-04-22 7:12 ` Guillaume Tucker
2019-04-23 8:37 ` Knut Omang
2019-04-23 10:22 ` Mark Rutland
2019-05-12 0:40 ` Andrea Parri
2019-05-22 15:52 ` Dmitry Vyukov
2019-05-23 14:03 ` Paul E. McKenney
2019-04-25 13:37 ` Veronika Kabatova
2019-04-26 21:02 ` Tim Bird
2019-05-16 0:39 ` Sasha Levin
2019-05-16 0:51 ` Tim.Bird
2019-05-22 16:04 ` Dmitry Vyukov
2019-05-22 16:07 ` Dhaval Giani
2019-05-22 15:48 ` Dmitry Vyukov
2019-05-23 0:07 ` Tim.Bird
2019-05-23 6:49 ` Dmitry Vyukov
2019-05-15 22:44 ` shuah [this message]
2019-05-15 23:19 ` Brendan Higgins
2019-05-16 0:36 ` Sasha Levin
2019-05-22 21:02 ` Brendan Higgins
2019-05-23 0:58 ` Steven Rostedt
2019-05-23 1:00 ` Steven Rostedt
2019-05-23 4:54 ` Knut Omang
2019-06-03 8:59 ` Brendan Higgins
2019-05-22 16:11 ` Dhaval Giani
2019-06-10 11:21 ` Douglas Raillard
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=3c6c9405-7e90-fb03-aa1c-0ada13203980@kernel.org \
--to=shuah@kernel.org \
--cc=alexander.levin@microsoft.com \
--cc=brendanhiggins@google.com \
--cc=dan.carpenter@oracle.com \
--cc=dhaval.giani@gmail.com \
--cc=dvyukov@google.com \
--cc=gustavo.padovan@collabora.co.uk \
--cc=khilman@baylibre.com \
--cc=knut.omang@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tbird20d@gmail.com \
--cc=willy@infradead.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
all inboxes | Powered by JetHome®