Linux-GPIO Archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linusw@kernel.org>
To: Rosen Penev <rosenp@gmail.com>
Cc: linux-gpio@vger.kernel.org,
	Bamvor Jian Zhang <bamv2005@gmail.com>,
	 Bartosz Golaszewski <brgl@kernel.org>,
	Kees Cook <kees@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: Fri, 20 Mar 2026 14:28:09 +0100	[thread overview]
Message-ID: <CAD++jL=ELqj0Cvd6WBG_UvAOt7+Y0xUPpc7qPEGS-0Dm2upYgA@mail.gmail.com> (raw)
In-Reply-To: <20260319000558.22108-1-rosenp@gmail.com>

On Thu, Mar 19, 2026 at 1:06 AM Rosen Penev <rosenp@gmail.com> wrote:

> Remove no longer needed kcalloc to simplify allocation.
>
> Added __counted_by along with a counting variable to get extra runtime
> analysis.
>
> Signed-off-by: Rosen Penev <rosenp@gmail.com>

Sweet!
Reviewed-by: Linus Walleij <linusw@kernel.org>

Yours,
Linus Walleij

  reply	other threads:[~2026-03-20 13:28 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 [this message]
2026-03-20 18:10 ` Kees Cook
2026-03-20 23:00   ` Rosen Penev
2026-03-23 10:00     ` Bartosz Golaszewski
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='CAD++jL=ELqj0Cvd6WBG_UvAOt7+Y0xUPpc7qPEGS-0Dm2upYgA@mail.gmail.com' \
    --to=linusw@kernel.org \
    --cc=bamv2005@gmail.com \
    --cc=brgl@kernel.org \
    --cc=gustavoars@kernel.org \
    --cc=kees@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).