From: Tom Rini <trini@ti.com>
To: Joe Perches <joe@perches.com>
Cc: Josh Triplett <josh@joshtriplett.org>,
<linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] checkpatch.pl: Add warning for new __packed additions
Date: Tue, 25 Feb 2014 07:30:56 -0500 [thread overview]
Message-ID: <530C8D00.8070606@ti.com> (raw)
In-Reply-To: <1393305803.11020.119.camel@joe-AO722>
On 02/25/2014 12:23 AM, Joe Perches wrote:
> On Mon, 2014-02-24 at 17:43 -0500, Tom Rini wrote:
>> My perl is quite limited, so however much effort you're interested in
>> putting in here is greatly appreciated (even if it's pointing out
>> something else already in the script to copy and modify). We already
>> ship a .checkpatch.conf so having to enable something by default is
>> fine. Thanks!
>
> The U-Boot checkpatch is not the same as the current
> linux version and would need updating.
>
> Tell me a little more please about how often or possible
> it would be to update the current linux version of
> checkpatch to the version used in U-Boot.
The only intentional differences we have today are adding debug/printf
to the list of log functions and pointing people at boards.cfg not
CHECKPATCH in MAINTAINERS, so I can re-sync us no problem as, yup, we're
about a year out of date there. Oh and I see now someone snuck in a
check for whitespace before semi-colon to catch 'return 0 ;' which I'll
check real quick isn't something already caught and if not post that as
well.
--
Tom
next prev parent reply other threads:[~2014-02-25 12:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 20:38 [PATCH] checkpatch.pl: Add warning for new __packed additions Tom Rini
2014-02-24 21:00 ` Joe Perches
2014-02-24 21:11 ` Tom Rini
2014-02-24 21:28 ` Joe Perches
2014-02-24 21:52 ` Tom Rini
2014-02-24 22:02 ` Joe Perches
2014-02-24 22:04 ` Tom Rini
2014-02-24 22:08 ` Joe Perches
2014-02-24 22:20 ` Tom Rini
2014-02-24 22:31 ` Joe Perches
2014-02-24 22:43 ` Tom Rini
2014-02-25 5:23 ` Joe Perches
2014-02-25 12:30 ` Tom Rini [this message]
2014-02-26 22:04 ` Joe Perches
2014-02-27 20:33 ` Tom Rini
2014-02-25 8:56 ` Heiko Carstens
2014-02-24 21:31 ` josh
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=530C8D00.8070606@ti.com \
--to=trini@ti.com \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=josh@joshtriplett.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