From: "Arnd Bergmann" <arnd@arndb.de>
To: "Jiri Pirko" <jiri@resnulli.us>, "Arnd Bergmann" <arnd@kernel.org>
Cc: "David S . Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Carolina Jubran" <cjubran@nvidia.com>,
"Tariq Toukan" <tariqt@nvidia.com>,
"Cosmin Ratiu" <cratiu@nvidia.com>,
"Mark Bloch" <mbloch@nvidia.com>,
"Simon Horman" <horms@kernel.org>,
"Joe Damato" <jdamato@fastly.com>,
"Przemek Kitszel" <przemyslaw.kitszel@intel.com>,
Netdev <netdev@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] devlink: move DEVLINK_ATTR_MAX-sized array off stack
Date: Wed, 09 Jul 2025 17:09:54 +0200 [thread overview]
Message-ID: <2d415391-82fa-4cf6-bc9b-ce845596a535@app.fastmail.com> (raw)
In-Reply-To: <dugteasq4zxwqww4hepsomjga4rxpyk76p5eudk7yrs74ub4vl@cusxvnvgmmtz>
On Wed, Jul 9, 2025, at 12:05, Jiri Pirko wrote:
> Tue, Jul 08, 2025 at 06:06:43PM +0200, arnd@kernel.org wrote:
>
> Isn't it about the time to start to leverage or cleanup infrastructure
> for things like this? /me covers against all the eggs flying in
> I mean, there are subsystems where it's perfectly fine to use it.
> Can we start with frees like this one and avoid the silly gotos?
I had so far resisted learning about how those actually work, thanks
for pushing me to finally trying it out ;-)
I've sent a v2 now.
Arnd
prev parent reply other threads:[~2025-07-09 15:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 16:06 [PATCH] devlink: move DEVLINK_ATTR_MAX-sized array off stack Arnd Bergmann
2025-07-09 10:03 ` Simon Horman
2025-07-09 10:05 ` Jiri Pirko
2025-07-09 15:09 ` Arnd Bergmann [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=2d415391-82fa-4cf6-bc9b-ce845596a535@app.fastmail.com \
--to=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=cjubran@nvidia.com \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jdamato@fastly.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=tariqt@nvidia.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.