From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] About B@D release, Renesas support and project-x
Date: Wed, 4 Oct 2017 11:01:31 +0200 [thread overview]
Message-ID: <59D4A36B.6080708@codethink.co.uk> (raw)
In-Reply-To: <00c901d33cdf$09a5c9f0$1cf15dd0$@toshiba.co.jp>
Hi,
On 04/10/17 09:04, Daniel Sangorrin wrote:
> Agustin, Chris:
>
>> -----Original Message-----
>> From: Agustin Benito Bethencourt [mailto:agustin.benito at codethink.co.uk]
>> Sent: Monday, October 02, 2017 11:14 PM
>> To: Daniel Sangorrin
>> Cc: cip-dev at lists.cip-project.org
>> Subject: About B at D release, Renesas support and project-x
>>
>> Hi Daniel,
>>
>> since you and Robert are doing activities that are related and need to
>> be done by ELCE, maybe it would be good to have a sync meeting to plan
>> them. I assume your request today at the TSC meeting goes in that direction.
>>
>> We usually meet on Thursdays but since Robert might need some time for
>> "landing" it might be better to have a video chat (or a call) on Friday.
>> Maybe Chris and others want to join.
>>
>> * What do you think?
>> * Which channel would you prefer?
>> * Which time slot have you available, considering the timezone difference?
>>
>> It would be a meeting for planning the technical tasks up to ELCE.
>
> Sorry, I'm going on holidays from Friday 6th to Monday 9th.
>
> My main concern during the TSC meeting was that I will only have 3 days
> next week (10th,11th and 13th) to integrate the Project-X LAVA demo with the latest B at D (LAVA 2017.7).
> # NOTE: the week after that I will not be available, and I will not be attending ELCE this year (Hayashi-san, Deby's maintainer, will instead).
> An update from Robert by e-mail on the status of LAVA 2017.7 (KernelCI is not used in the Demo) on B at D would be enough for me.
> I just want to know when to start the integration.
Ah, there are further agenda issue. I understand. No problem. As soon as
Robert is back and landed, he (or myself) will contact you directly with
the info.
>
> Actually, there is a bigger problem. The physical demo requires a remote power switch and unfortunately we
> haven't been able to obtain the necessary documentation for export control. For that reason, I have decided
> to record it on video and prepare some slides explaining Project-X instead of showing a live demo.
I see.
>
> Thanks,
> Daniel
>
>
>
>
>
>
>
> Thanks,
> Daniel
>
>> --
>> Agustin Benito Bethencourt
>> Principal Consultant - FOSS at Codethink
>> agustin.benito at codethink.co.uk
>
>
>
>
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk
prev parent reply other threads:[~2017-10-04 9:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 14:14 [cip-dev] About B@D release, Renesas support and project-x Agustin Benito Bethencourt
2017-10-02 14:56 ` Chris Paterson
2017-10-04 7:04 ` Daniel Sangorrin
2017-10-04 9:01 ` Agustin Benito Bethencourt [this message]
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=59D4A36B.6080708@codethink.co.uk \
--to=agustin.benito@codethink.co.uk \
--cc=cip-dev@lists.cip-project.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