All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alison Schofield <alison.schofield@intel.com>
To: Kloudifold <cloudifold.3125@gmail.com>
Cc: outreachy@lists.linux.dev
Subject: Re: Problem in "Pick a warning, and try to fix it": Don't have a warning to pick
Date: Wed, 8 Mar 2023 15:59:16 -0800	[thread overview]
Message-ID: <ZAkhVJfWLk5mcyON@aschofie-mobl2> (raw)
In-Reply-To: <ZAkE4w/T389R2+Er@CloudiRingWorld>

On Thu, Mar 09, 2023 at 05:57:55AM +0800, Kloudifold wrote:
> Hello, I am Kloudifold, an Outreachy applicant.
> 
> I'm reading https://kernelnewbies.org/Outreachyfirstpatch and trying to make my first patch. It says, "Pick a warning, and try to fix it. For your first patch, only pick one warning.", but when I used the command:
> 
> > perl scripts/checkpatch.pl -f drivers/staging/*/* | grep "[1-9] warnings" -B 10 -A 2

Hi Kloudifold,

Your script is quitting after operating on the first dir. 

There are more WARNINGs and CHECKs 
Look up the --strict option to checkpatch to get those CHECKs.

Reminder: don't include drivers/staging/media in your searches.

Alison
> 
> I can only find warnings for drivers/staging/axis-fifo/axis-fifo.c, a file that is already being submitted to the mailing list, which means I don't have a warning to pick.
> How should I finish my first patch in this case? Should I look for something more difficult than changing the coding style?
> 

  reply	other threads:[~2023-03-08 23:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08 21:57 Problem in "Pick a warning, and try to fix it": Don't have a warning to pick Kloudifold
2023-03-08 23:59 ` Alison Schofield [this message]
2023-03-09  6:29 ` Julia Lawall

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=ZAkhVJfWLk5mcyON@aschofie-mobl2 \
    --to=alison.schofield@intel.com \
    --cc=cloudifold.3125@gmail.com \
    --cc=outreachy@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.