From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Rosen Penev <rosenp@gmail.com>, linux-rtc@vger.kernel.org
Cc: Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
"moderated list:ARM/Marvell Kirkwood and Armada 370, 375,
38x,..." <linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] rtc: armada38x: zalloc + calloc to single allocation
Date: Thu, 05 Mar 2026 09:41:03 +0100 [thread overview]
Message-ID: <871phyfz34.fsf@BLaptop.bootlin.com> (raw)
In-Reply-To: <20260304225329.24510-1-rosenp@gmail.com>
Rosen Penev <rosenp@gmail.com> writes:
> Use a flexible array member to simplify allocation.
>
I must admit that I didn't know struct_size(), it is a nice helper!
Reviewed-by: Gregory CLEMENT <gregory.clement@bootlin.com>
Thanks,
Gregory
> Signed-off-by: Rosen Penev <rosenp@gmail.com>
> ---
> drivers/rtc/rtc-armada38x.c | 9 ++-------
> 1 file changed, 2 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/rtc/rtc-armada38x.c b/drivers/rtc/rtc-armada38x.c
> index 713fa0d077cd..245290ae1a8d 100644
> --- a/drivers/rtc/rtc-armada38x.c
> +++ b/drivers/rtc/rtc-armada38x.c
> @@ -72,8 +72,8 @@ struct armada38x_rtc {
> spinlock_t lock;
> int irq;
> bool initialized;
> - struct value_to_freq *val_to_freq;
> const struct armada38x_rtc_data *data;
> + struct value_to_freq val_to_freq[];
> };
>
> #define ALARM1 0
> @@ -490,18 +490,13 @@ static __init int armada38x_rtc_probe(struct platform_device *pdev)
> {
> struct armada38x_rtc *rtc;
>
> - rtc = devm_kzalloc(&pdev->dev, sizeof(struct armada38x_rtc),
> + rtc = devm_kzalloc(&pdev->dev, struct_size(rtc, val_to_freq, SAMPLE_NR),
> GFP_KERNEL);
> if (!rtc)
> return -ENOMEM;
>
> rtc->data = of_device_get_match_data(&pdev->dev);
>
> - rtc->val_to_freq = devm_kcalloc(&pdev->dev, SAMPLE_NR,
> - sizeof(struct value_to_freq), GFP_KERNEL);
> - if (!rtc->val_to_freq)
> - return -ENOMEM;
> -
> spin_lock_init(&rtc->lock);
>
> rtc->regs = devm_platform_ioremap_resource_byname(pdev, "rtc");
> --
> 2.53.0
>
--
Grégory CLEMENT, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-03-05 8:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 22:53 [PATCH] rtc: armada38x: zalloc + calloc to single allocation Rosen Penev
2026-03-05 8:41 ` Gregory CLEMENT [this message]
2026-03-05 8:51 ` Rosen Penev
2026-03-13 10:26 ` Alexandre Belloni
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=871phyfz34.fsf@BLaptop.bootlin.com \
--to=gregory.clement@bootlin.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=rosenp@gmail.com \
--cc=sebastian.hesselbarth@gmail.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