![]() ![]() I would suggest not posting anything to these maillists unless you’re an applicant or participant of these programs. ![]() Īnother great place to learn is from the maillists of various mentorship programs related to Linux kernel. You can also subscribe to their maillist. ![]() The best place is #kernelnewbies channel on. Please follow this tutorial - Your First Kernel Patch But please remember to be respectful and polite with your communication. You can contribute to this process by helping developers in improving/fixing their code. Once enough people agree on the patch, it gets merged. People submit their patches and community gives comments on them. Bug fixing generally requires some familiarity with code-base and the patch submission process.Īs I mentioned earlier, all the Linux kernel work happens in public over maillists. There are many bugs found in the Linux kernel by various tools and users. You canĮither tackle the TODO items, &/ can do a simple coding style Parent directory, that lists things that need to be done to it. Up to kernel coding style, or use deprecated API. Staging tree, in drivers/staging/ is full of drivers that are not quite You can attempt the task to find such files(.txt) and convert them The documentation but many documentation files are not yet following Linux kernel documentation can be found here - under the Documentation directory of the Linux kernel source code - Įxists guidelines and tools to enforce proper structure and format to #1: FILE: drivers/staging/mt7621-dts/mt7621.dtsi:1:ĬHECK: Blank lines aren’t necessary before a close brace ’}’ WARNING: Missing or malformed SPDX-License-Identifier tag in line 1 + write_gcr_reg1_mask(mask | CM_GCR_REGn_MASK_CMTGT_IOCU0) #160: FILE: drivers/staging/mt7621-dma/mtk-hsdma.c:160:ĬHECK: Alignment should match open parenthesis WARNING: Missing a blank line after declarations Warning looks like and why it is a good idea to get your linux kernel Purpose of this list is to give you the idea of what a checkpatch The below warnings were present at time of writing thisīlog, someone might have fixed it by the time you are reading this. Please go through the Linux kernel coding style - īefore attempting to fix any of the following warnings. Many kernel developers on various IRC channels. Apart from the mailgroups, you can also find The discussion happens in public over this mail groups and personalĮmails are discouraged. In the Linux kernel world, all communication happens via maillists.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |