[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAAq6er2K2TaBm_NUgs5E7LbWhZZLwd_kNzPf=kpbtCvccr7kRw@mail.gmail.com>
Date: Fri, 20 Jan 2012 12:18:45 +0000
From: Andy Whitcroft <apw@...onical.com>
To: Dan Carpenter <dan.carpenter@...cle.com>
Cc: Pradheep Shrinivasan <pradheep.sh@...il.com>, greg@...ah.com,
devel@...uxdriverproject.org, swetland@...gle.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/6] staging:android_pmem.h: Fixes the space and other
formating issues pointed out by checkpatch.pl
On Fri, Jan 20, 2012 at 11:54 AM, Dan Carpenter
<dan.carpenter@...cle.com> wrote:
> It still complains about the following macros where parenthesis are
> not needed.
>
> ERROR: Macros with complex values should be enclosed in parenthesis
> #156: FILE: staging/android/pmem.c:156:
> +#define PMEM_IS_FREE(id, index) !(pmem[id].bitmap[index].allocated)
>
> Let's just make the check look for an operator with a low
> precedence.
> http://en.wikipedia.org/wiki/Order_of_operations#Programming_languages
>
> Otherwise the submitters are going to change it to:
>
> #define PMEM_IS_FREE(id, index) (!(pmem[id].bitmap[index].allocated))
>
> That has two pairs of unneeded paranthesis and we run the risk of
> reprogramming the kernel in lisp, by mistake.
Yep we want to avoid that. As -> binds tighter than many of the
operators in these bands we can only safely avoid the ()'s if the
operator does not potentially make a pointer, so for now I have added
unary minus and the two unary not operators. I think I want to see
some examples of other operators before I would be keen to have any
further exceptions.
Anyhow how does this work for you:
http://people.canonical.com/~apw/checkpatch/checkpatch-next.pl
-apw
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists