Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] llvm/clang
Date: Tue, 16 Jan 2018 15:10:38 +0100	[thread overview]
Message-ID: <20180116151038.3d27d2d0@windsurf> (raw)
In-Reply-To: <eea8291f-5cdc-3cb3-3df0-9dac033d9025@smile.fr>

Hello,

On Tue, 16 Jan 2018 10:25:39 +0100, Valentin KORENBLIT wrote:

> As an intern at Smile (Paris), I will be working for 6 months on the integration
> of LLVM/Clang for Buildroot, on top of what has already been done by Romain
> Naour and others [1].

Great!

> Feel free to send me any suggestions, advice or whatever you believe it is
> necessary to be considered for this patch. I am available on IRC in the
> Buildroot channel as vkorenblit.

Welcome, and looking forward to meeting you during the Buildroot
Developers Meeting next month in Brussels!

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

      reply	other threads:[~2018-01-16 14:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-16  9:25 [Buildroot] llvm/clang Valentin KORENBLIT
2018-01-16 14:10 ` Thomas Petazzoni [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=20180116151038.3d27d2d0@windsurf \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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