Re: picking the first patch

2021-03-21 Thread Valdis Klētnieks
On Sun, 21 Mar 2021 12:03:36 -0400, Harsha Vardhan said: > So far I have spent a lot of time dreaming to be a kernel hacker without > doing much , 1) What Greg said.. :) 2) Go read this: https://lists.kernelnewbies.org/pipermail/kernelnewbies/2017-April/017765.html And yes, *why* you want to

Re: picking the first patch

2021-03-21 Thread Lukas Bulwahn
On Sun, Mar 21, 2021 at 5:25 PM Harsha Vardhan wrote: > > perfect ! I will do it that way then. > > besides that, generally if you are making changes to drivers , then the > responsibility of testing is on the author of the patch right ? if you don't > have the device how would you test such

Re: picking the first patch

2021-03-21 Thread Harsha Vardhan
perfect ! I will do it that way then. besides that, generally if you are making changes to drivers , then the responsibility of testing is on the author of the patch right ? if you don't have the device how would you test such things ? I would assume other subsystems like memory will have some

Re: picking the first patch

2021-03-21 Thread Greg KH
On Sun, Mar 21, 2021 at 12:03:36PM -0400, Harsha Vardhan wrote: > Any thoughts on whether I should just do a checkpatch.pl change as my first > patch ? You should do a checkpatch.pl change as your first patch :) That way you can focus on the process more than the technical aspects of the patch

picking the first patch

2021-03-21 Thread Harsha Vardhan
Hello team , Sorry for a vague question. So far I have spent a lot of time dreaming to be a kernel hacker without doing much , but I realised its geting too late and now I want to pick my first patch to work, I have decided to address the TODO at drivers/staging/grebus/TODO : " * Make pwm.c use