![]() Jonathan Corbet of LWN, he noted, is good at this already, but there are several people doing it each their own way in their own space. Putting all the kernel documentation found around the Internet together is itself a full-time job. It is hard enough for Linux kernel developers to keep up with the Linux Kernel Mailing List, Landley noted, let alone to read all the other lists out there and keep track of the ever-growing supply of documentation. But there is a big integration problem, as such sources of documentation are scattered around. When a source of some documentation for some item gains enough traction, it becomes the de facto source of documentation for that particular subsection of the kernel, and from then on gets found and maintained. The challenge in providing useful documentation for the Linux kernel, Landley said, is therefore to index what is already out there. Where, asked Landley, is kernel documentation? It’s in the kernel tarball, on the Web, in magazines, in recordings from conferences like OLS, in man pages, on list archives, on developers’ blogs, and “that’s just the tip of the iceberg.” The major problem is not a lack of documentation, he said, but that what is out there is not indexed. He explained that it was meant to be a year, but after six months he had come to some conclusions about how documentation should be done, which he said the Linux Foundation both agreed with and did not plan to pursue, and so he went back to maintaining his other projects. Landley did a six-month fellowship with the Linux Foundation last year to try to improve the Linux kernel’s documentation. After that, if you still have any questions, ask on the kernelnewbies mailing list or in the #kernelnewbies IRC channel.The second of four days at the 10th annual Ottawa Linux Symposium got off to an unusual start as a small bird “assisted” Rob Landley in giving the first talk I attended, called “ Where Linux kernel documentation hides.” The tweeting bird was polite, only flying over the audience a couple of times and mostly paying attention. To learn more, read the KernelNewbies First Kernel Patch tutorial. The Eudyptula challenge is a great way to learn kernel basics.(All questions were answered, and this way saves reading time.) (Notice that the last question was unintentionally left unanswered in the reply.) Do you want to schedule the meeting tomorrow? Yes let’s schedule the meeting tomorrow, on the second floor. Note: Do not top-post to communicate with the reviewer of your patch! Here's an example:.Go through the linux.git log to see commits by previous authors for inspiration.Coccinelle is a helpful tool for pattern matching.You could complete TODOs left incomplete by developers:.Perl scripts/ -f drivers/staging/android/* | less The script detects coding style errors for you. ![]() To learn more, read the Linux kernel coding style documentation. You also could start with correcting coding style issues in the code.When you get familiar with the patch-sending process, you could send subsystem-specific patches with increased complexity. Greg Kroah-Hartman's staging tree is a good place to submit your first patch as he accepts easy patches from new contributors.What to know before submitting your first patch To know the list of maintainers to whom to send the patch, use the get_ script. Free online course: RHEL Technical Overview.Step 7: Commit your changes and create a patch. Recompile using make command to ensure that your change does not produce errors. Git rebase origin/staging-testing Step 6: Make a change to the code base. git checkout -b first-patch Step 5: Update your kernel to point to the latest code base. Sudo make modules_install install Step 4: Make a branch and switch to it. config Step 3: Build/install your kernel. Git:///pub/scm/linux/kernel/git/gregkh/staging.git Copy your current config: cp /boot/config-`uname -r`*. ![]() ![]() Step 2: Download the Linux kernel code repository : git clone -b staging-testing Steps in this article assume you have the following tools on your system: Contributing to the kernel Step 1: Prepare your system. For a more in-depth look at the submission process for contributing your first patch, read the KernelNewbies First Kernel Patch tutorial. In this article, I'll provide a quick checklist of steps involved with making your first kernel contribution, and look at what you should know before submitting a patch. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |