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

;{{SpeakerInfo}}: {{Speaker|Андрей Шевченко}}
<blockquote>
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.
</blockquote>

{{VideoSection}}
{{vimeoembed|223913334|800|450}}
{{youtubelink|BLzw_pdjV8U}}{{letscomment}}
{{SlidesSection}}
[[File:Typical mistakes when submitting a new code to Linux kernel (Andy Shevchenko, LVEE-2017).pdf|left|page=-|300px]]

{{----}}

== Thesis ==

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

<references/>
[[File:{{#setmainimage:Typical mistakes when submitting a new code to Linux kernel (Andy Shevchenko, LVEE-2017)!.jpg}}|center|640px]]




{{stats|disqus_comments=0|refresh_time=2018-05-15T17:02:312021-08-31T16:39:57.355425497592|vimeo_comments=0|vimeo_plays=2067|youtube_comments=10|youtube_plays=60116}}

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