From: me@felipebalbi.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] [v2] omap:mailbox-enhancements and fixes
Date: Wed, 10 Nov 2010 21:17:36 +0200 [thread overview]
Message-ID: <1289416656.16560.15.camel@eowin> (raw)
In-Reply-To: <4CDAEB5C.6000703@ti.com>
Hi,
On Wed, 2010-11-10 at 19:58 +0100, Cousson, Benoit wrote:
> My point was that checkpatch is supposed to check patch... but it's true
> that is can check the code as well. I was assuming that all the code in
> mainline is supposed to be already checkpatch proof :-)
> It seems that this is not the case.
>
> It might be interesting to run it on every plat-omap / mach-omap files...
you might be surprised with the results :-)
--
balbi
next prev parent reply other threads:[~2010-11-10 19:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 12:45 [PATCH 0/6] [v2] omap:mailbox-enhancements and fixes Hari Kanigeri
2010-11-10 12:45 ` [PATCH 1/6] mailbox: change full flag per mailbox queue instead of global Hari Kanigeri
2010-11-10 12:45 ` [PATCH 2/6] omap:mailbox: fix rx interrupt disable in omap4 Hari Kanigeri
2010-11-10 12:45 ` [PATCH 3/6] omap:mailbox-fix checkpatch warnings Hari Kanigeri
2010-11-10 16:49 ` Sergei Shtylyov
2010-11-10 12:45 ` [PATCH 4/6] omap:mailbox-send message in process context Hari Kanigeri
2010-11-10 12:45 ` [PATCH 5/6] omap:mailbox-add notification support for multiple readers Hari Kanigeri
2010-11-10 12:45 ` [PATCH 6/6] omap:clocks44x-add dummy clock for mailbox Hari Kanigeri
2010-11-10 23:27 ` Paul Walmsley
2010-11-11 1:37 ` Hari Kanigeri
2010-11-10 16:40 ` [PATCH 0/6] [v2] omap:mailbox-enhancements and fixes Cousson, Benoit
2010-11-10 16:56 ` Hari Kanigeri
2010-11-10 18:58 ` Cousson, Benoit
2010-11-10 19:17 ` Felipe Balbi [this message]
2010-11-10 19:02 ` Cousson, Benoit
2010-11-10 16:52 ` Cousson, Benoit
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=1289416656.16560.15.camel@eowin \
--to=me@felipebalbi.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).