All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alison Schofield <amsfield22@gmail.com>
To: Anchal Jain <anchalj109@gmail.com>
Cc: Daniel Baluta <daniel.baluta@gmail.com>,
	Greg KH <gregkh@linuxfoundation.org>,
	outreachy-kernel <outreachy-kernel@googlegroups.com>
Subject: Re: [Outreachy kernel] Doubts Regaarding the checkpatch.pl
Date: Thu, 15 Sep 2016 21:50:46 -0700	[thread overview]
Message-ID: <20160916045044.GA2835@d830.WORKGROUP> (raw)
In-Reply-To: <CAAbeOSsVJn8Ed9B+acg1BRXRnmixDouk9z1ijGy5LnU2isSz1w@mail.gmail.com>

On Thu, Sep 15, 2016 at 11:02:50PM +0530, Anchal Jain wrote:
> > Can you give a real example for the CHECK? :)
> 
> like this
> 
>  CHECK: Unnecessary parentheses around padapter->mlmeextpriv
>  CHECK: Please don't use multiple blank lines
>  CHECK: Unnecessary parentheses around pstapriv->sta_hash_lock
>  CHECK: Unnecessary parentheses around pstapriv->sta_hash_lock
>  CHECK: Unnecessary parentheses around pmlmeext->mlmext_info
>  CHECK: Concatenated strings should use spaces between elements
> 
> 
> Thanks,
> 
> On Thu, Sep 15, 2016 at 10:44 PM, Daniel Baluta <daniel.baluta@gmail.com>
> wrote:
> 
> > On Thu, Sep 15, 2016 at 7:53 PM, Anchal Jain <anchalj109@gmail.com> wrote:
> > >
> > >>I'm sorry, but I can not parse this, can you rephrase it?
> > >
> > > When we run checkpatch.pl on our staging directory then it shows
> > > - Errors
> > > - Warnings
> > > - Checks
> > >
> > > So I want to know if we solve the check using checkpatch.pl tool then
> > it is
> > > consider in our patches
> > > or Only those checks is consider which is solved using  cocci script
> > because
> > > this script also fixes those
> > > checks

Here's my take, let me know if I got the question right?

Sometime the cocci script identifies and maybe also corrects (if you are using
the patch option) issues that were also found by checkpatch.  So, the
question perhaps is which tool you would mention in your log message?

I'd say both. You would say the issue was found and fixed with
coccinelle and also corrects checkpatch issue: ....

Or, maybe I don't have the question right ;)

alisons








> >
> > Can you give a real example for the CHECK? :)
> >
> 
> -- 
> You received this message because you are subscribed to the Google Groups "outreachy-kernel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com.
> To post to this group, send email to outreachy-kernel@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/CAAbeOSsVJn8Ed9B%2Bacg1BRXRnmixDouk9z1ijGy5LnU2isSz1w%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.


  reply	other threads:[~2016-09-16  4:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-15 15:53 Doubts Regaarding the checkpatch.pl Anchal Jain
2016-09-15 16:38 ` [Outreachy kernel] " Greg KH
2016-09-15 16:53   ` Anchal Jain
2016-09-15 17:14     ` Daniel Baluta
2016-09-15 17:32       ` Anchal Jain
2016-09-16  4:50         ` Alison Schofield [this message]
2016-09-17 10:55           ` Anchal Jain

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=20160916045044.GA2835@d830.WORKGROUP \
    --to=amsfield22@gmail.com \
    --cc=anchalj109@gmail.com \
    --cc=daniel.baluta@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=outreachy-kernel@googlegroups.com \
    /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.