From: Joe Perches <joe@perches.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Julia Lawall <julia.lawall@lip6.fr>,
Dan Carpenter <dan.carpenter@oracle.com>,
Clemens Ladisch <clemens@ladisch.de>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>
Subject: Re: RFC: kernel coding style: prefer array to &array[0] ?
Date: Wed, 01 Jul 2015 16:04:13 -0700 [thread overview]
Message-ID: <1435791853.12101.131.camel@perches.com> (raw)
In-Reply-To: <20150701223311.GE36579@dtor-ws>
On Wed, 2015-07-01 at 15:33 -0700, Dmitry Torokhov wrote:
> On Wed, Jul 01, 2015 at 07:53:44AM -0700, Joe Perches wrote:
> > On Wed, 2015-07-01 at 14:26 +0200, Julia Lawall wrote:
> > > On Wed, 1 Jul 2015, Dan Carpenter wrote:
> > > > On Wed, Jul 01, 2015 at 01:54:29PM +0200, Clemens Ladisch wrote:
> > > > > Joe Perches wrote:
> > > > > > It seems most in-kernel uses are 'array' rather than '&array[0]'
> > > > > >
> > > > > > Most of the time, using array is simpler to read than &array[0].
> > > > > >
> > > > > > Exceptions exists when addresses for consecutive members are
> > > > > > used like func(&array[0], &array[1]);
> > > > >
> > > > > I use '&array[0]' when I want to get a pointer to a single object that
> > > > > happens to be the first one in an array.
> > > >
> > > > Yeah. Of course, you're right. Otherwise it ends up confusing static
> > > > checkers if you want the first element or the whole array.
> >
> > Right.
> >
> > > > > > Should this preference be put into checkpatch and/or CodingStyle?
> >
> > And checkpatch will have no idea what the prototype
> > for any function is, so this transform is better left
> > for smarter tools like coccinelle.
> >
> > The proper answer here is no.
[]
> CHECK: Using addressof array 'mtouch->data' index [0] may be simpler as
> 'mtouch->data'
> #97: FILE: drivers/input/touchscreen/mtouch.c:97:
> + if (MTOUCH_FORMAT_TABLET_STATUS_BIT & mtouch->data[0])
The joys of perl parsing.
> CHECK: Using addressof array 'msg' index [0] may be simpler as 'msg'
> #38: FILE: drivers/input/touchscreen/ipaq-micro-ts.c:38:
> + be16_to_cpup((__be16 *) &msg[0]));
That's using the first member in an array.
> I'd be OK with changing cases like:
>
> CHECK: Using addressof array 'buf' index [0] may be simpler as 'buf'
> #232: FILE: drivers/input/touchscreen/zforce_ts.c:232:
> + return zforce_send_wait(ts, &buf[0], ARRAY_SIZE(buf));
I think cases like those are sensible to change.
cheers, Joe
next prev parent reply other threads:[~2015-07-01 23:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 17:35 RFC: kernel coding style: prefer array to &array[0] ? Joe Perches
2015-07-01 6:10 ` Julia Lawall
2015-07-01 11:54 ` Clemens Ladisch
2015-07-01 12:15 ` Dan Carpenter
2015-07-01 12:26 ` Julia Lawall
2015-07-01 14:53 ` Joe Perches
2015-07-01 22:33 ` Dmitry Torokhov
2015-07-01 23:04 ` Joe Perches [this message]
2015-07-05 21:28 ` Julia Lawall
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=1435791853.12101.131.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=clemens@ladisch.de \
--cc=dan.carpenter@oracle.com \
--cc=dmitry.torokhov@gmail.com \
--cc=julia.lawall@lip6.fr \
--cc=lgirdwood@gmail.com \
--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 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.