From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Rosen Penev <rosenp@gmail.com>, Linus Walleij <linusw@kernel.org>
Cc: linux-gpio@vger.kernel.org, Daniel Palmer <daniel@thingy.jp>,
linux-hardening@vger.kernel.org, gustavoars@kernel.org,
Romain Perier <romain.perier@gmail.com>,
Bartosz Golaszewski <brgl@kernel.org>,
"moderated list:ARM/MStar/Sigmastar Armv7 SoC support"
<linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] gpio: msc313: remove kcalloc
Date: Mon, 9 Mar 2026 12:17:39 +0900 [thread overview]
Message-ID: <7dac0a99-0883-4ec1-9bfd-49b659bd38e6@embeddedor.com> (raw)
In-Reply-To: <CAKxU2N9JbAzEYfmLpbw5b9Y6MsYUZ1FfLirfy8Hg8MCOUY6PAg@mail.gmail.com>
On 3/9/26 10:27, Rosen Penev wrote:
> On Sun, Mar 8, 2026 at 5:06 PM Linus Walleij <linusw@kernel.org> wrote:
>>
>> On Sun, Mar 8, 2026 at 3:15 AM Rosen Penev <rosenp@gmail.com> wrote:
>>
>>> Use a flexible array member to combine kzalloc and kcalloc.
>>>
>>> Signed-off-by: Rosen Penev <rosenp@gmail.com>
>> (...)
>>> struct msc313_gpio {
>>> void __iomem *base;
>>> const struct msc313_gpio_data *gpio_data;
>>
>> Do you wanna add:
>>
>> const unsigned int saved_size;
> So in the code there's
>
> for (i = 0; i < gpio->gpio_data->num; i++)
>
> which is equivalent to match->num.
>
> __counted_by doesn't support pointers AFAIK.
We actually have __counted_by_ptr().
-Gustavo
next prev parent reply other threads:[~2026-03-09 18:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-08 2:15 Rosen Penev
2026-03-08 5:59 ` Daniel Palmer
2026-03-09 0:06 ` Linus Walleij
2026-03-09 1:27 ` Rosen Penev
2026-03-09 3:17 ` Gustavo A. R. Silva [this message]
2026-03-09 9:03 ` Bartosz Golaszewski
2026-03-09 22:00 ` Rosen Penev
2026-03-10 8:51 ` Bartosz Golaszewski
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=7dac0a99-0883-4ec1-9bfd-49b659bd38e6@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=brgl@kernel.org \
--cc=daniel@thingy.jp \
--cc=gustavoars@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=romain.perier@gmail.com \
--cc=rosenp@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
all inboxes | Powered by JetHome®