From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: Rosen Penev <rosenp@gmail.com>, linux-clk@vger.kernel.org
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
Alim Akhtar <alim.akhtar@samsung.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Brian Masney <bmasney@redhat.com>, Kees Cook <kees@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
"open list:SAMSUNG SOC CLOCK DRIVERS"
<linux-samsung-soc@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
open "list:KERNEL" HARDENING "(not" covered by other
"areas):Keyword:b__counted_by(_le|_be)?b"
<linux-hardening@vger.kernel.org>
Subject: Re: [PATCHv2 0/3] clk: samsung: use kzalloc_flex
Date: Thu, 7 May 2026 11:32:53 +0300 [thread overview]
Message-ID: <4c57b107-e1eb-4eef-ad77-021d9669900d@linaro.org> (raw)
In-Reply-To: <20260506233833.178357-1-rosenp@gmail.com>
Hi!
On 5/7/26 2:38 AM, Rosen Penev wrote:
> Switch three structs to flexible array members to combine allocations.
>
What's changed in v2?
Cheers,
ta
> Rosen Penev (3):
> v2: fix compilation and reword descriptions
> clk: samsung: use kzalloc_flex
> clk: samsung: cpu: use kzalloc_flex
> clk: samsung: pll: use kzalloc_flex
>
> drivers/clk/samsung/clk-cpu.c | 34 +++++++++------------
> drivers/clk/samsung/clk-pll.c | 56 ++++++++++++++++-------------------
> drivers/clk/samsung/clk.c | 11 +++----
> drivers/clk/samsung/clk.h | 2 +-
> 4 files changed, 47 insertions(+), 56 deletions(-)
>
next prev parent reply other threads:[~2026-05-07 8:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 23:38 [PATCHv2 0/3] clk: samsung: use kzalloc_flex Rosen Penev
2026-05-06 23:38 ` [PATCHv2 1/3] " Rosen Penev
2026-05-07 23:34 ` Brian Masney
2026-05-06 23:38 ` [PATCHv2 2/3] clk: samsung: cpu: " Rosen Penev
2026-05-06 23:38 ` [PATCHv2 3/3] clk: samsung: pll: " Rosen Penev
2026-05-07 8:32 ` Tudor Ambarus [this message]
2026-05-07 8:43 ` [PATCHv2 0/3] clk: samsung: " Rosen Penev
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=4c57b107-e1eb-4eef-ad77-021d9669900d@linaro.org \
--to=tudor.ambarus@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=bmasney@redhat.com \
--cc=cw00.choi@samsung.com \
--cc=gustavoars@kernel.org \
--cc=kees@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=rosenp@gmail.com \
--cc=s.nawrocki@samsung.com \
--cc=sboyd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox