Typical mistakes when submitting a new code to Linux kernel (Andy Shevchenko, LVEE-2017) — различия между версиями

== Thesis ==

{{LinksSection}}
* [https://lvee.org/ru/abstracts/240 Talks page]
<!-- <blockquote>[©]</blockquote> -->


<references/>





{{stats|disqus_comments=0|refresh_time=2018-035-01T18:07:4315T17:02:31.236847355425|vimeo_comments=0|vimeo_plays=1420|youtube_comments=01|youtube_plays=4660}}

[[Категория:LVEE-2017]]
[[Категория:Linux]]
[[Категория:Процесс разработки]]

Версия 14:02, 15 мая 2018

Докладчик

Андрей Шевченко

Code review is a crucial part of developing a stable and robust open source project, such as Linux kernel. New comers and surprisingly many active and known contributors have been doing same mistakes, like using non-scalable APIs, over and over. How can we eliminate or avoid them? Looking at the patterns the best practices would be suggested. In addition, relatively new Linux kernel APIs, such as Unified Device Properties, will be discussed.

Видео

on youtube

Презентация

Thesis

Примечания и ссылки

• Talks page

Plays:80   Comments:1