From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [cip-members] CIP Workshop at ELCE: B@D 101 training session. Call for registration
Date: Thu, 19 Oct 2017 10:35:45 +0200 [thread overview]
Message-ID: <59E863E1.3000206@codethink.co.uk> (raw)
In-Reply-To: <c797bb40d22d4ed8946079f54b42f4c6@RVC-EX13-M02.rvc.renesas.com>
Hi,
On 19/10/17 07:45, Binh Thanh. Nguyen wrote:
> Hello,
>
> I hope it still has a slot for me.
> * Name : Binh Nguyen
> * Company : Renesas Design Vietnam
> * Position/role : Developer
> * Why you are interested on this workshop : we are working to make CIP B at D support Renesas board, It is helpful to do some practice with main developer behind B at D
> * Are you coming with your own board or do you need one? I Renesas board, but unfortunately I cannot carry it on flight. So I will need a board.
I am currently in an event but as soon as I have a slot I will add you
to the list in the wiki. See you on Sunday.
>
> Best regards,
> Binh Nguyen
>
>
>> -----Original Message-----
>> From: cip-members-bounces at lists.cip-project.org [mailto:cip-members-
>> bounces at lists.cip-project.org] On Behalf Of Agustin Benito Bethencourt
>> Sent: Thursday, September 28, 2017 9:27 PM
>> To: cip-members at lists.cip-project.org
>> Subject: [cip-members] CIP Workshop at ELCE: B at D 101 training session. Call
>> for registration
>>
>> Dear CIP friends,
>>
>> ELCE is approaching and CIP will organise a Workshop on Sunday 22nd October
>> at the ELCE location. This is the day before the event starts.
>>
>> ++ B at D 101 training session
>>
>> One of the main activities of that workshop is a Board At Desk (our CIP testing
>> environment) training session. We have called the activity "B at D
>> 101 training".
>>
>> There will have room for 10 participants and Robert Marshall will be the one
>> providing it. He is the main developer behind B at D.
>>
>> You can find all the information in the CIP wiki[1], including the time and some
>> instructions.
>>
>> I will send to this mailing list and will add to the wiki the room at the ELCE
>> venue where the workshop will take place.
>>
>> ++ What do I need to do to participate?
>>
>> As described on the wiki, you will need to send to this mailing list a mail with
>> some basic information about yourself.
>>
>> * Name
>> * Company
>> * Position/role
>> * Why you are interested on this workshop.
>> * Are you coming with your own board or do you need one?
>>
>> Please keep in mind that you need to bring your laptop and a BeagleBone
>> Black. If you do not have such board, we will have 5 spare Renesas boards
>> (thanks Renesas).
>>
>> This is why it will be important that you tell us if you are coming with your own
>> board or not. After sending the mail, I will add you to the wiki on first comes
>> first served basis.
>>
>> Do not hesitate to ask any question through this mailing list or directly to me. I
>> will answer them as soon as possible.
>>
>> I hope to see you there.
>>
>> [1]
>> https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipconferences/ci
>> pwselce2017#b-d-101how-to-test-the-cip-kernel-using-b-d
>>
>> Best Regards
>> --
>> Agustin Benito Bethencourt
>> Principal Consultant - FOSS at Codethink agustin.benito at codethink.co.uk
>> _______________________________________________
>> cip-members mailing list
>> cip-members at lists.cip-project.org
>> https://lists.cip-project.org/mailman/listinfo/cip-members
>
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk
prev parent reply other threads:[~2017-10-19 8:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <59CD06B6.5020805@codethink.co.uk>
2017-10-19 5:45 ` [cip-dev] [cip-members] CIP Workshop at ELCE: B@D 101 training session. Call for registration Binh Thanh. Nguyen
2017-10-19 8:35 ` 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=59E863E1.3000206@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 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.