[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0iLe9nCk0xtfAdfEYqvUiWESvDoQi_RWJ6LK1T6h4CqKg@mail.gmail.com>
Date: Fri, 5 Jan 2024 16:48:00 +0100
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Christophe JAILLET <christophe.jaillet@...adoo.fr>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>, Daniel Lezcano <daniel.lezcano@...aro.org>,
Zhang Rui <rui.zhang@...el.com>, Lukasz Luba <lukasz.luba@....com>, alexis.lothore@...tlin.com,
linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org,
linux-pm@...r.kernel.org
Subject: Re: [PATCH] thermal: core: Save a few bytes of memory when
registering a cooling device
On Fri, Jan 5, 2024 at 3:55 PM Christophe JAILLET
<christophe.jaillet@...adoo.fr> wrote:
>
> Le 05/01/2024 à 14:50, Rafael J. Wysocki a écrit :
> > On Fri, Jan 5, 2024 at 2:45 PM Christophe JAILLET
> > <christophe.jaillet@...adoo.fr> wrote:
> >>
> >> Some *thermal_cooling_device_register() calls pass a string literal as the
> >> 'type' parameter.
> >>
> >> So kstrdup_const() can be used instead of kfree() to avoid a memory
> >
> > I guess you mean kstrdup()?
>
> Sure.
> Stupid cut'n'paste typo. Thx for catching it.
>
> Should I resend, or can it be fixed if/when the patch is applied?
I can fix it up.
Powered by blists - more mailing lists