All of lore.kernel.org
 help / color / mirror / Atom feed
From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: Vijay Kumar <vijaykumar@bravegnu.org>
Cc: LTP List <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [RFC] Using checkpatch.pl
Date: Tue, 30 Jun 2009 13:11:03 +0530	[thread overview]
Message-ID: <1246347663.4819.26.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <1245346301.5041.36.camel@subratamodak.linux.ibm.com>

Vijay,

Are you working on such a patch ?

Regards--
Subrata

On Thu, 2009-06-18 at 23:01 +0530, Subrata Modak wrote: 
> Send across a patch:
> 1) adding checkpatch.pl to LTP,
> 2) those instructions/future suggestions you have mentioned, update the
> same in README.
> 
> Also remember to send patches against it in future when checkpatch.pl is
> updated in the kernel tree itself.
> 
> Regards--
> Subrata
> 
> On Sun, 2009-06-14 at 22:03 +0530, Vijay Kumar wrote: 
> > Hi everyone,
> > Michal Simek patched most of the LTP code base to use the Linux kernel
> > coding style. But unfortunately new patches, that are flowing in, seem
> > to add coding style violations. It is better to prevent new style
> > violations than to fix them later on.
> > 
> > The kernel developers use a perl script called checkpatch.pl to
> > identify style violations in patches. We could use the same script to
> > check our patches, as well. The script uses files from the kernel to
> > do kernel specific checks. This can be disabled by using the --no-tree
> > option. So to check an LTP patch
> > 
> > $ checkpatch.pl --no-tree ltp-patch
> > 
> > If everybody is OK with it we can add the script to the LTP source
> > tree, so that everyone checks their patches against the same
> > script. And Subrata can easily check for style violations before
> > merging the patch.
> > 
> > In the future, we could also customize the script to do userspace/LTP
> > specific checks, like missing mode argument when open() is invoked
> > with O_CREAT flag.
> > 
> > Please do send in your suggestions.
> > 
> > Regards,
> > Vijay
> > 
> > ------------------------------------------------------------------------------
> > Crystal Reports - New Free Runtime and 30 Day Trial
> > Check out the new simplified licensing option that enables unlimited
> > royalty-free distribution of the report engine for externally facing 
> > server and web deployment.
> > http://p.sf.net/sfu/businessobjects
> > _______________________________________________
> > Ltp-list mailing list
> > Ltp-list@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/ltp-list
> 
> 
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables unlimited
> royalty-free distribution of the report engine for externally facing 
> server and web deployment.
> http://p.sf.net/sfu/businessobjects
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list


------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2009-06-30  7:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-14 16:33 [LTP] [RFC] Using checkpatch.pl Vijay Kumar
2009-06-15  2:38 ` Garrett Cooper
2009-06-15  7:17   ` Mike Frysinger
2009-06-18 17:31 ` Subrata Modak
2009-06-30  7:41   ` Subrata Modak [this message]
2009-06-30  8:37     ` Vijay Kumar

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=1246347663.4819.26.camel@subratamodak.linux.ibm.com \
    --to=subrata@linux.vnet.ibm.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=vijaykumar@bravegnu.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 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.