From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: "Jérémy Lefaure" <jeremy.lefaure@lse.epita.fr>
Cc: Peter Huewe <peterhuewe@gmx.de>,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 13/18] tpm: use ARRAY_SIZE
Date: Wed, 11 Oct 2017 14:48:26 +0300 [thread overview]
Message-ID: <20171011114826.kvzfweerdavsa6tf@linux.intel.com> (raw)
In-Reply-To: <20171010163011.2df093d1@blatinox-laptop.localdomain>
On Tue, Oct 10, 2017 at 04:30:11PM -0400, Jeremy Lefaure wrote:
> On Wed, 4 Oct 2017 15:14:49 +0300
> Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> wrote:
>
> > On Sun, Oct 01, 2017 at 03:30:51PM -0400, Jeremy Lefaure wrote:
> > > Using the ARRAY_SIZE macro improves the readability of the code.
> > >
> > > Found with Coccinelle with the following semantic patch:
> > > @r depends on (org || report)@
> > > type T;
> > > T[] E;
> > > position p;
> > > @@
> > > (
> > > (sizeof(E)@p /sizeof(*E))
> > > |
> > > (sizeof(E)@p /sizeof(E[...]))
> > > |
> > > (sizeof(E)@p /sizeof(T))
> > > )
> > >
> > > Signed-off-by: Jeremy Lefaure <jeremy.lefaure@lse.epita.fr>
> >
> > Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> >
> Hi Jarkko,
> This patch is an individual patch, it's not really part of a series
> (my fault, sorry).
>
> Could you apply this patch to your tree ?
>
> Thank you,
> Jeremy
It is already applied :-)
I'll take it as part of my next pull request. Thank you.
/JarkkO
next prev parent reply other threads:[~2017-10-11 11:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-01 19:30 [PATCH 00/18] use ARRAY_SIZE macro Jérémy Lefaure
2017-10-01 19:30 ` [PATCH 13/18] tpm: use ARRAY_SIZE Jérémy Lefaure
2017-10-04 12:14 ` Jarkko Sakkinen
2017-10-10 20:30 ` Jérémy Lefaure
2017-10-11 11:48 ` Jarkko Sakkinen [this message]
2017-10-01 22:01 ` [PATCH 00/18] use ARRAY_SIZE macro Tobin C. Harding
2017-10-02 0:52 ` Jérémy Lefaure
2017-10-02 5:35 ` Greg KH
2017-10-02 19:22 ` J. Bruce Fields
2017-10-03 1:33 ` Jérémy Lefaure
2017-10-05 17:57 ` J. Bruce Fields
2017-10-02 16:37 ` Mauro Carvalho Chehab
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=20171011114826.kvzfweerdavsa6tf@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=jeremy.lefaure@lse.epita.fr \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
/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).