lkmp:lkmp_first_kernel_patch
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
lkmp:lkmp_first_kernel_patch [2019/04/08 19:26] ShuahKhanLF |
lkmp:lkmp_first_kernel_patch [2019/08/08 22:22] (current) ShuahKhanLF |
||
|---|---|---|---|
| Line 280: | Line 280: | ||
| Once you have the name of a driver, it's time to find out where the .c and .h files for that driver are in the Linux kernel repository. You can do that by searching through the Makefiles to find out what C files are compiled into the driver binary. The best way to do that is with "**git grep**". Unlike normal grep, git grep only searches through checked-in files in the repository. Normal grep will also search the binary files, and even the .git directory, which isn't useful and wastes your time. | Once you have the name of a driver, it's time to find out where the .c and .h files for that driver are in the Linux kernel repository. You can do that by searching through the Makefiles to find out what C files are compiled into the driver binary. The best way to do that is with "**git grep**". Unlike normal grep, git grep only searches through checked-in files in the repository. Normal grep will also search the binary files, and even the .git directory, which isn't useful and wastes your time. | ||
| - | For example, if you wanted to search for the files that are compiled into the xhci-hcd driver, you would run this command: | + | For example, if you wanted to search for the files that are compiled into the uvcvideo driver, you would run this command: |
| <code> | <code> | ||
| Line 390: | Line 390: | ||
| </code> | </code> | ||
| - | Search for your pr_info in the log file by typing "**/I changed**". You should be able to find this message within the driver output during boot. If you don't see this message, ask for help on the #kernelnewbies IRC channel on irc.oftc.net, or on the linux-kernel-mentees mailing list | + | Search for your pr_info in the log file by typing "**/I changed**". You should be able to find this message within the driver output during boot. If you don't see this message, ask for help on the #linux-kernel-mentees IRC Channel on [[https://freenode.net/|freenode]] irc.freenode.net, or on the linux-kernel-mentees mailing list |
| ==== Revert your changes ==== | ==== Revert your changes ==== | ||
| Line 527: | Line 527: | ||
| </code> | </code> | ||
| - | Now, I run `make menuconfig` and type '/' to search for USB_XHCI_HCD. The search entry shows: | + | Now, I run "**make menuconfig**" and type "**/**" to search for USB_XHCI_HCD. The search entry shows: |
| <code> | <code> | ||
| Line 842: | Line 842: | ||
| ==== Versioning patchsets ==== | ==== Versioning patchsets ==== | ||
| - | When you send out a new version of a patchset, you could either indicate on each patch what has changed or you could include the changes in a coverletter. If you plan to indicate the changes in each patch, you need to specify what has changed in each version like in this [[https://lkml.org/lkml/2018/2/23/287|patch example]] and indicate "**No change**" explicitly for patch versions that are unaltered. In case you decide to indicate the changes in a coverletter, here is an [[http://marc.info/?l=linux-usb&m=139302798628519&w=2|Example cover letter.]] You can include a coverletter in your patchset by using the `--cover-letter` option to `git format-patch`, e.g. | + | When you send out a new version of a patchset, you could either indicate on each patch what has changed or you could include the changes in a coverletter. If you plan to indicate the changes in each patch, you need to specify what has changed in each version like in this [[https://lkml.org/lkml/2018/2/23/287|patch example]] and indicate "**No change**" explicitly for patch versions that are unaltered. In case you decide to indicate the changes in a coverletter, here is an [[http://marc.info/?l=linux-usb&m=139302798628519&w=2|Example cover letter.]] You can include a coverletter in your patchset by using the "**--cover-letter**" option to "**git format-patch**", e.g. |
| <code> | <code> | ||
lkmp/lkmp_first_kernel_patch.1554751614.txt.gz · Last modified: 2019/04/08 19:26 by ShuahKhanLF
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
