picking the first patch

[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 sort of test suite that gets
run automatically to make sure we are not introducing any regressions but
confused as to how we ensure the same with drivers.

Thanks so much Greg , for a quick reply .

On Sun, Mar 21, 2021 at 12:14 PM Greg KH <greg at kroah.com> wrote:

> 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 (git, changelog text, subject line, email, submission,
> revision, acceptance, etc.) and not have to worry a lot about breaking
> working code or not.
>
> After you get the process working properly for you, then move to
> changing real code and contributing that way.
>
> But that's just a suggestion, not a requirement, you can do whatever you
> want to do :)
>
> good luck!
>
> greg k-h
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20210321/fd115ec9/attachment.html>