mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <Tim.Bird@sony.com>
To: <sashal@kernel.org>, <tbird20d@gmail.com>
Cc: <vkabatov@redhat.com>, <dhaval.giani@gmail.com>,
	<alexander.levin@microsoft.com>, <shuah@kernel.org>,
	<khilman@baylibre.com>, <linux-kernel@vger.kernel.org>,
	<rostedt@goodmis.org>, <dan.carpenter@oracle.com>,
	<willy@infradead.org>, <gustavo.padovan@collabora.co.uk>,
	<dvyukov@google.com>, <knut.omang@oracle.com>,
	<eslobodo@redhat.com>
Subject: RE: Linux Testing Microconference at LPC
Date: Thu, 16 May 2019 00:51:37 +0000	[thread overview]
Message-ID: <ECADFF3FD767C149AD96A924E7EA6EAF9771A6DF@USCULXMSG01.am.sony.com> (raw)
In-Reply-To: <20190516003915.GT11972@sasha-vm>



> -----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



  reply	other threads:[~2019-05-16  1:47 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 [this message]
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
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=ECADFF3FD767C149AD96A924E7EA6EAF9771A6DF@USCULXMSG01.am.sony.com \
    --to=tim.bird@sony.com \
    --cc=alexander.levin@microsoft.com \
    --cc=dan.carpenter@oracle.com \
    --cc=dhaval.giani@gmail.com \
    --cc=dvyukov@google.com \
    --cc=eslobodo@redhat.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=sashal@kernel.org \
    --cc=shuah@kernel.org \
    --cc=tbird20d@gmail.com \
    --cc=vkabatov@redhat.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®