public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sayyad Abid <sayyad.abid16@gmail.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH]The patch fixes the following warning generated by running the
Date: Wed, 21 Aug 2024 23:14:09 +0530	[thread overview]
Message-ID: <ZsYnadjCVKpR2Thv@debian> (raw)
In-Reply-To: <00cc036e-6e12-4c9d-9c97-953c452606f3@stanley.mountain>

On Wed, Aug 21, 2024 at 08:37:26PM +0300, Dan Carpenter wrote:
> On Wed, Aug 21, 2024 at 10:54:17PM +0530, Sayyad Abid wrote:
> > On Wed, Aug 21, 2024 at 07:57:30PM +0300, Dan Carpenter wrote:
> > > Also the subject is not in the correct format.
> > >
> > > regards,
> > > dan carpenter
> > >
> > Noted, I'll keep this in mind from further patches. Also could you please guide
> > to a fairly updated TODO list or somewhere from where I could look for tasks to
> > start. The lists I found in the kernel tree all are too old to be left with any
> > task, I apologise if I am asking a stupid thing.
>
> Please always keep the mailing lists in the CC.
>
> Try searching for KTODO on lore.  Maybe that will produce some useful ideas.
> https://lore.kernel.org/all/?q=KTODO
>
> Try running checkpatch or Smatch on drivers/staging/media/atomisp/
>
> regards,
> dan carpenter
Thank you for mentioning the TODOs. I'll look into the KTODO and checkpatch.
I'll also make sure to keep the list in the cc.

      parent reply	other threads:[~2024-08-21 17:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-21 16:15 [PATCH]The patch fixes the following warning generated by running the Sayyad Abid
2024-08-21 16:56 ` Dan Carpenter
2024-08-21 16:57 ` Dan Carpenter
     [not found]   ` <ZsYiwZDh3yegyERk@debian>
     [not found]     ` <00cc036e-6e12-4c9d-9c97-953c452606f3@stanley.mountain>
2024-08-21 17:44       ` Sayyad Abid [this message]

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=ZsYnadjCVKpR2Thv@debian \
    --to=sayyad.abid16@gmail.com \
    --cc=dan.carpenter@linaro.org \
    --cc=linux-kernel@vger.kernel.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