From: Joe Perches <joe@perches.com>
To: Rasmus Villemoes <rasmus.villemoes@prevas.dk>,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
linux-kernel@vger.kernel.org
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-media@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Kees Cook <keescook@chromium.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
Ian Abbott <abbotti@mev.co.uk>
Subject: Re: [PATCH][RFC] kernel.h: provide array iterator
Date: Fri, 16 Mar 2018 11:45:43 -0700 [thread overview]
Message-ID: <1521225943.6119.10.camel@perches.com> (raw)
In-Reply-To: <b6af11b9-d697-59ec-6acc-80f0657a3e11@prevas.dk>
On Fri, 2018-03-16 at 16:27 +0100, Rasmus Villemoes wrote:
> On 2018-03-15 11:00, Kieran Bingham wrote:
> > Simplify array iteration with a helper to iterate each entry in an array.
> > Utilise the existing ARRAY_SIZE macro to identify the length of the array
> > and pointer arithmetic to process each item as a for loop.
I recall getting negative feedback on a similar proposal
a decade ago:
https://lkml.org/lkml/2007/2/13/25
Not sure this is different.
next prev parent reply other threads:[~2018-03-16 18:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 10:00 [PATCH][RFC] kernel.h: provide array iterator Kieran Bingham
2018-03-16 4:21 ` Kees Cook
2018-03-16 6:41 ` Julia Lawall
2018-03-16 7:31 ` Kieran Bingham
2018-03-16 15:27 ` Rasmus Villemoes
2018-03-16 18:45 ` Joe Perches [this message]
2018-03-17 10:12 ` Kieran Bingham
2018-03-17 9:32 ` Kieran Bingham
-- strict thread matches above, loose matches on Subject: below --
2018-03-16 19:40 Alexey Dobriyan
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=1521225943.6119.10.camel@perches.com \
--to=joe@perches.com \
--cc=abbotti@mev.co.uk \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=keescook@chromium.org \
--cc=kieran.bingham@ideasonboard.com \
--cc=krzk@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rasmus.villemoes@prevas.dk \
--cc=rdunlap@infradead.org \
--cc=tglx@linutronix.de \
--cc=yamada.masahiro@socionext.com \
/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