From: Bartosz Golaszewski <brgl@kernel.org>
To: Rosen Penev <rosenp@gmail.com>
Cc: Kees Cook <kees@kernel.org>,
linux-gpio@vger.kernel.org,
Bamvor Jian Zhang <bamv2005@gmail.com>,
Linus Walleij <linusw@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@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: [PATCH] gpio: mockup: allocate lines with main struct
Date: Mon, 23 Mar 2026 11:00:10 +0100 [thread overview]
Message-ID: <CAMRc=MctGTeqBHQ8zaQ7_2YAoWoTUxOK4_hs+-EHEQEPnz+A-g@mail.gmail.com> (raw)
In-Reply-To: <CAKxU2N8ZZp5fcCWfMaqZ9VKwNQ3a06fsQPXpBQa-d1N07zPGng@mail.gmail.com>
On Sat, Mar 21, 2026 at 12:00 AM Rosen Penev <rosenp@gmail.com> wrote:
>
> >
> > static int gpio_mockup_probe(struct platform_device *pdev)
> > {
> > ...
> > u16 ngpio;
> > ...
> > rv = device_property_read_u16(dev, "nr-gpios", &ngpio);
> > ...
> > gc->ngpio = ngpio;
> > ...
> > chip->lines = devm_kcalloc(dev, gc->ngpio,
> > sizeof(*chip->lines), GFP_KERNEL);
> >
> > But this begs the question: why add nr_lines when ngpio is already part
> > of the struct:
> Maintainers for some inexplicable reason want an extra variable for
> __counted_by works.
I believe what Kees means here is: you can use ngpio for __counted_by() like so:
__counted_by(gc.ngpio)
I didn't think about it and I do prefer it of course over an extra field.
Bart
next prev parent reply other threads:[~2026-03-23 10:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 0:05 [PATCH] gpio: mockup: allocate lines with main struct Rosen Penev
2026-03-20 13:28 ` Linus Walleij
2026-03-20 18:10 ` Kees Cook
2026-03-20 23:00 ` Rosen Penev
2026-03-23 10:00 ` Bartosz Golaszewski [this message]
2026-03-23 16:43 ` Rosen Penev
2026-03-24 9:16 ` Bartosz Golaszewski
2026-03-24 15:51 ` Rosen Penev
2026-03-24 15:54 ` Bartosz Golaszewski
2026-03-24 15:56 ` Rosen Penev
2026-03-24 17:16 ` Bartosz Golaszewski
2026-03-24 18:25 ` 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='CAMRc=MctGTeqBHQ8zaQ7_2YAoWoTUxOK4_hs+-EHEQEPnz+A-g@mail.gmail.com' \
--to=brgl@kernel.org \
--cc=bamv2005@gmail.com \
--cc=gustavoars@kernel.org \
--cc=kees@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).