kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: Harsha Vardhan <harshavardhan3294@gmail.com>
To: kernelnewbies@kernelnewbies.org
Subject: picking the first patch
Date: Sun, 21 Mar 2021 12:03:36 -0400	[thread overview]
Message-ID: <CAO=Zo81bVP-9fZxB1VYV061SE8NJkcnLKrBx_04VBYwybxjwjA@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 664 bytes --]

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 the struct pwm_ops::apply instead of ::config,
::set_polarity,
  4   ::enable and ::disable."

To make sure this is a first good patch , I verified that there is traction
for this driver recently.

But I am not sure, let's say I change the code , how to test it ?

Any thoughts on whether I should just do a checkpatch.pl change as my first
patch ?

Thanks
Vardhan

[-- Attachment #1.2: Type: text/html, Size: 919 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

             reply	other threads:[~2021-03-21 16:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-21 16:03 Harsha Vardhan [this message]
2021-03-21 16:14 ` picking the first patch Greg KH
2021-03-21 16:25   ` Harsha Vardhan
2021-03-21 17:34     ` Lukas Bulwahn
2021-03-22  5:56 ` Valdis Klētnieks

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAO=Zo81bVP-9fZxB1VYV061SE8NJkcnLKrBx_04VBYwybxjwjA@mail.gmail.com' \
    --to=harshavardhan3294@gmail.com \
    --cc=kernelnewbies@kernelnewbies.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).