Someone here probably knows this, so I figured I'd ask: I submitted a small patch to the kernel a while back and I made a typo in it and it broke the tests, and then I couldn't figure out how to get the test bot to pick up my new patch and by that point I assume anyone who would possibly have reviewed my patch stopped bothering. Is there something I should do to get it looked at again?
Linux Kernel Teaching
21–30 of 82 posts
Re: Linux Kernel Teaching
#22Someone here probably knows this, so I figured I'd ask: I submitted a small patch to the kernel a while back and I made a typo in it and it broke the tests, and then I couldn't figure out how to get the test bot to pick up my new patch and by that point I assume anyone who would possibly have reviewed my patch stopped bothering. Is there something I should do to get it looked at again?
E-mail the person maintaining the sub-system you are modifying.
Re: Linux Kernel Teaching
#23Someone here probably knows this, so I figured I'd ask: I submitted a small patch to the kernel a while back and I made a typo in it and it broke the tests, and then I couldn't figure out how to get the test bot to pick up my new patch and by that point I assume anyone who would possibly have reviewed my patch stopped bothering. Is there something I should do to get it looked at again?
E-mail the person maintaining the sub-system you are modifying.
I had Al Viro CC'd on the emails when I sent it to linux-fsdevel. Are you saying I should send it to him again, directly? (The patch, for reference: https://github.com/saagarjha/linux/commit/4867a403decc364c8b.... I figured I should also take this opportunity to check to make sure there's nothing wrong with it that might cause it to be ignored.)
Re: Linux Kernel Teaching
#24Cool, thank you very much!
Re: Linux Kernel Teaching
#25Earlier quoted context omitted.
E-mail the person maintaining the sub-system you are modifying.
I had Al Viro CC'd on the emails when I sent it to linux-fsdevel. Are you saying I should send it to him again, directly? (The patch, for reference: https://github.com/saagarjha/linux/commit/4867a403decc364c8b... . I figured I should also take this opportunity to check to make sure there's nothing wrong with it that might cause it to be ignored.)
Yes, if you know him personally; no otherwise
Re: Linux Kernel Teaching
#26Earlier quoted context omitted.
I had Al Viro CC'd on the emails when I sent it to linux-fsdevel. Are you saying I should send it to him again, directly? (The patch, for reference: https://github.com/saagarjha/linux/commit/4867a403decc364c8b... . I figured I should also take this opportunity to check to make sure there's nothing wrong with it that might cause it to be ignored.)
Yes, if you know him personally; no otherwise
I do not, unfortunately :(
Re: Linux Kernel Teaching
#27The Linux Foundation recently released a free course as well titled "A Beginner's Guide to Linux Kernel Development" - haven't taken it yet, but another resource for the community: https://training.linuxfoundation.org/resources/free-courses/...
Here's another freely available beginner's resource on Linux internals by u/0xAX [0]: https://0xax.gitbooks.io/linux-insides/content/index.html
Re: Linux Kernel Teaching
#28Awesome! I can't wait to dig through this, I've been wanting to contribute to the linux kernel for over 2 years but no one on the linux mailing lists seemed interested in helping a newbie (so much for kernel newbies). Thanks for putting this together.
I find other systems (such as netbsd) to have a fairly more readable codebase and friendlier community. It was very easy for me to make some contributions there.
NetBSD to me seemed to have the most readable codebase, even compared to other BSDs.
Re: Linux Kernel Teaching
#29Someone here probably knows this, so I figured I'd ask: I submitted a small patch to the kernel a while back and I made a typo in it and it broke the tests, and then I couldn't figure out how to get the test bot to pick up my new patch and by that point I assume anyone who would possibly have reviewed my patch stopped bothering. Is there something I should do to get it looked at again?
If your original patch contained a mistake, you just send the new version with the v2 prefix to the mailing list. You can do this with git format-patch -v2 and then send-email will pick it up automatically.
You should note the change in the individual commit or the cover letter.
Re: Linux Kernel Teaching
#30Started getting into kernel stuff for work. Does anyone have a good idea what kind of market demand there is for kernel devs or similar skill sets? Being new to this I absolutely love it, but have no idea.
The resources shared by everyone here are so helpful! I’ve been muddling through by reading the docs, source code, and various messages on the mailing list and... it’s been a little painful.