From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Reviewing the Buildroot ELC presentation slides
Date: Tue, 7 Feb 2012 22:46:11 +0100 [thread overview]
Message-ID: <20120207224611.0d9e45d5@skate> (raw)
Hello,
I have posted at http://free-electrons.com/~thomas/pub/buildroot.pdf
the current version of the slides I intend to present next week at the
ELC in San Francisco.
For the record, the conference abstract is:
https://events.linuxfoundation.org/events/embedded-linux-conference/petazzoni
I would be very interested in your comments and review, both on details
(typos, mistakes) but also on the overall contents of the slides.
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next reply other threads:[~2012-02-07 21:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 21:46 Thomas Petazzoni [this message]
2012-02-08 7:02 ` [Buildroot] Reviewing the Buildroot ELC presentation slides Thomas De Schampheleire
2012-02-08 7:23 ` Thomas De Schampheleire
2012-02-08 8:05 ` Peter Korsgaard
2012-02-08 8:46 ` Samuel Martin
2012-02-08 11:24 ` Will Moore
2012-02-14 14:11 ` Thomas Petazzoni
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=20120207224611.0d9e45d5@skate \
--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