From: Kevin Hilman <khilman@baylibre.com>
To: linux-omap@vger.kernel.org, Rosen Penev <rosenp@gmail.com>
Cc: Aaro Koskinen <aaro.koskinen@iki.fi>,
Andreas Kemnade <andreas@kemnade.info>,
Roger Quadros <rogerq@kernel.org>,
Tony Lindgren <tony@atomide.com>,
Russell King <linux@armlinux.org.uk>,
Kees Cook <kees@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCHv3] ARM: omap2: simplify allocation for omap_device
Date: Mon, 11 May 2026 09:51:53 -0700 [thread overview]
Message-ID: <177851831304.45285.1551367657338168278.b4-ty@b4> (raw)
In-Reply-To: <20260330213528.18187-1-rosenp@gmail.com>
On Mon, 30 Mar 2026 14:35:28 -0700, Rosen Penev wrote:
> Use a flexible array member (FAM) to combine hwmods array allocation
> with the omap_device structure. This reduces the number of allocations
> from two separate calls (one for the device, one for the array) to a
> single allocation, improving efficiency and reducing memory fragmentation.
>
> The FAM approach also enables bounds checking through __counted_by(),
> which provides runtime verification that array accesses stay within
> the allocated size. This improves security and helps catch bugs during
> development.
>
> [...]
Applied, thanks!
[1/1] ARM: omap2: simplify allocation for omap_device
commit: 2a7a9e20b9e8b5dc4fdef777e67d390dcb3a8ea4
Best regards,
--
Kevin Hilman (TI) <khilman@baylibre.com>
prev parent reply other threads:[~2026-05-11 16:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 21:35 [PATCHv3] ARM: omap2: simplify allocation for omap_device Rosen Penev
2026-05-08 19:12 ` Kevin Hilman
2026-05-11 16:51 ` Kevin Hilman [this message]
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=177851831304.45285.1551367657338168278.b4-ty@b4 \
--to=khilman@baylibre.com \
--cc=aaro.koskinen@iki.fi \
--cc=andreas@kemnade.info \
--cc=gustavoars@kernel.org \
--cc=kees@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=rogerq@kernel.org \
--cc=rosenp@gmail.com \
--cc=tony@atomide.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