From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: platform-driver-x86@vger.kernel.org, Rosen Penev <rosenp@gmail.com>
Cc: Kenneth Chan <kenneth.t.chan@gmail.com>,
Hans de Goede <hansg@kernel.org>, Kees Cook <kees@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH] platform/x86: panasonic-laptop: simplify allocation of sinf
Date: Mon, 11 May 2026 20:53:05 +0300 [thread overview]
Message-ID: <177852198558.27853.167418180738728210.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20260430221555.83351-1-rosenp@gmail.com>
On Thu, 30 Apr 2026 15:15:55 -0700, Rosen Penev wrote:
> Change to a flexible array member to allocate once instead of twice.
>
> Use __counted_by for extra runtime analysis. Move the counting
> variable assignment to right after allocation as done by
> kzalloc_flex for GCC 15 and above.
>
> Remove + 1 to allocation. It's already done in the previous line.
>
> [...]
Thank you for your contribution, it has been applied to my local
review-ilpo-next branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-next branch only once I've pushed my
local branch there, which might take a while.
The list of commits applied:
[1/1] platform/x86: panasonic-laptop: simplify allocation of sinf
commit: a3d0dbd18ce908292607bb6cf37c978ece8a33d4
--
i.
next prev parent reply other threads:[~2026-05-11 17:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 22:15 [PATCH] platform/x86: panasonic-laptop: simplify allocation of sinf Rosen Penev
2026-05-11 17:53 ` Ilpo Järvinen [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-20 0:49 Rosen Penev
2026-03-20 18:32 ` Kees Cook
2026-03-20 23:02 ` Rosen Penev
2026-03-23 9:13 ` Ilpo Järvinen
2026-03-23 16:44 ` 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=177852198558.27853.167418180738728210.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=gustavoars@kernel.org \
--cc=hansg@kernel.org \
--cc=kees@kernel.org \
--cc=kenneth.t.chan@gmail.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.