From: Thomas Gleixner <tglx@kernel.org>
To: Rosen Penev <rosenp@gmail.com>, linux-kernel@vger.kernel.org
Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
"moderated list:ARM/STM32 ARCHITECTURE"
<linux-stm32@st-md-mailman.stormreply.com>,
"moderated list:ARM/STM32 ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] irqchip: stm32-exti: use kzalloc_flex
Date: Wed, 11 Mar 2026 09:46:31 +0100 [thread overview]
Message-ID: <87ms0erbx4.ffs@tglx> (raw)
In-Reply-To: <20260311054038.166293-1-rosenp@gmail.com>
On Tue, Mar 10 2026 at 22:40, Rosen Penev wrote:
> Simplifies allocations by using a flexible array member in these structs.
> No need for a second kfree.
Nice, but please follow the guidelines in
https://www.kernel.org/doc/html/latest/process/maintainer-tip.html
regarding subject prefix and function notations in change logs.
Thanks,
tglx
prev parent reply other threads:[~2026-03-11 8:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 5:40 [PATCH] irqchip: stm32-exti: use kzalloc_flex Rosen Penev
2026-03-11 8:46 ` Thomas Gleixner [this message]
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=87ms0erbx4.ffs@tglx \
--to=tglx@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@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