From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] Self-nomination
Date: Fri, 29 Jul 2016 14:57:51 +0300 [thread overview]
Message-ID: <2030690.Q1F2ncv1Ea@avalon> (raw)
Hello,
I would like to nominate myself for the Kernel Summit 2016.
My current areas of activity in the Linux kernel are the media (for media
controller and V4L2) and graphics subsystems, where I hack on both the core
frameworks and device drivers.
The topics proposed this year that I'm particularly interested in are
- Probe ordering, device dependencies and asynchronous probing, especially
given their direct impact on embedded media and graphics devices (in the
functional sense) that are usually made of multiple kernel devices (in the
struct device sense).
- Sensors and subsystem boundaries. As the co-author of the media controller
API (with Sakari Ailus, based on a proposal from Hans Verkuil) I've tried to
bridge the gap between the media, sound and graphics subsystems for a long
time. Lessons learnt there can be of interest to the other areas of the kernel
now being impacted by the same issue.
- Testing infrastructure and unit testing, wearing both my programmer and
technical evangelist hats. This could overlap partially with the regression
tracking topic.
If the documentation and maintainership topics get discussed (in sessions or
during the hallway track) I would like to participate as well.
--
Regards,
Laurent Pinchart
next reply other threads:[~2016-07-29 11:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 11:57 Laurent Pinchart [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-07-29 16:31 [Ksummit-discuss] self-nomination Stephen Hemminger
2016-07-27 14:27 [Ksummit-discuss] Self-nomination Jason Cooper
2016-07-27 16:19 ` Jonathan Cameron
2016-07-28 18:16 ` Laurent Pinchart
2016-07-26 2:28 [Ksummit-discuss] self-nomination Wangnan (F)
2016-07-23 20:36 Benjamin Herrenschmidt
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=2030690.Q1F2ncv1Ea@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=ksummit-discuss@lists.linuxfoundation.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