[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <05402205-bbe1-617c-d43e-205b0d238508@linaro.org>
Date: Wed, 7 Jun 2023 15:17:28 +0200
From: Daniel Lezcano <daniel.lezcano@...aro.org>
To: Saeed Mahameed <saeed@...nel.org>
Cc: rafael@...nel.org, linux-pm@...r.kernel.org,
thierry.reding@...il.com, Sandipan Patra <spatra@...dia.com>,
Gal Pressman <gal@...dia.com>,
Saeed Mahameed <saeedm@...dia.com>,
Jakub Kicinski <kuba@...nel.org>,
Leon Romanovsky <leon@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Paolo Abeni <pabeni@...hat.com>,
"open list:MELLANOX MLX5 core VPI driver" <netdev@...r.kernel.org>,
"open list:MELLANOX MLX5 core VPI driver"
<linux-rdma@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/8] net/mlx5: Update the driver with the recent thermal
changes
On 01/06/2023 00:10, Saeed Mahameed wrote:
> On 25 May 16:01, Daniel Lezcano wrote:
>> The thermal framework is migrating to the generic trip points. The set
>> of changes also implies a self-encapsulation of the thermal zone
>> device structure where the internals are no longer directly accessible
>> but with accessors.
>>
>> Use the new API instead, so the next changes can be pushed in the
>> thermal framework without this driver failing to compile.
>>
>> No functional changes intended.
>>
>
> I see this patch is part of a large series, do you expect me to re-post to
> net-next or you are going to submit via another tree ?
Sorry for the delay.
Yes, this patch is targeted for the thermal tree. The last patch of the
series depends on it as it moves the thermal zone device structure to
the private thermal header, thus the structure internals won't be
accessible from this driver anymore.
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
Powered by blists - more mailing lists