[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <751f786a3ceee08eff698633c39bb3a6b4b2f6d1.camel@nvidia.com>
Date: Wed, 4 Jun 2025 22:40:39 +0000
From: Timur Tabi <ttabi@...dia.com>
To: "christophe.jaillet@...adoo.fr" <christophe.jaillet@...adoo.fr>,
"philip.li@...el.com" <philip.li@...el.com>, "simona@...ll.ch"
<simona@...ll.ch>, "lyude@...hat.com" <lyude@...hat.com>,
"pierre.morrow@...e.fr" <pierre.morrow@...e.fr>, "airlied@...il.com"
<airlied@...il.com>, "jacob.e.keller@...el.com" <jacob.e.keller@...el.com>,
"dakr@...nel.org" <dakr@...nel.org>, Ben Skeggs <bskeggs@...dia.com>
CC: "dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
"nouveau@...ts.freedesktop.org" <nouveau@...ts.freedesktop.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] drm/nouveau/bl: Use kasprintf for interface name
On Wed, 2025-06-04 at 15:16 -0700, Jacob Keller wrote:
> Fair enough. Another alternative which saves the stack and macro would
> be to add a new version of backlight_register_device which can pass the
> integer number itself into dev_set_name, but thats probably not worth
> the churn either. (Currently we snprintf into a buffer and then again
> copy that again into the device name...)
If you really wanted to avoid stack space, you could add backlist_name[24] to 'struct
nouveau_backlight'.
Powered by blists - more mailing lists