lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 31 May 2022 09:38:03 +0700
From:   Bagas Sanjaya <bagasdotme@...il.com>
To:     Guenter Roeck <linux@...ck-us.net>,
        Sasha Levin <sashal@...nel.org>, linux-kernel@...r.kernel.org,
        stable@...r.kernel.org
Cc:     jdelvare@...e.com, corbet@....net, linux-hwmon@...r.kernel.org,
        linux-doc@...r.kernel.org
Subject: Re: [PATCH AUTOSEL 5.17 128/135] hwmon: Make chip parameter for
 with_info API mandatory

On 5/30/22 21:27, Guenter Roeck wrote:
> On 5/30/22 06:31, Sasha Levin wrote:
>> From: Guenter Roeck <linux@...ck-us.net>
>>
>> [ Upstream commit ddaefa209c4ac791c1262e97c9b2d0440c8ef1d5 ]
>>
>> Various attempts were made recently to "convert" the old
>> hwmon_device_register() API to devm_hwmon_device_register_with_info()
>> by just changing the function name without actually converting the
>> driver. Prevent this from happening by making the 'chip' parameter of
>> devm_hwmon_device_register_with_info() mandatory.
>>
>> Signed-off-by: Guenter Roeck <linux@...ck-us.net>
>> Signed-off-by: Sasha Levin <sashal@...nel.org>
> 
> This patch should not be backported. It is only relevant for new
> kernel releases, and may have adverse affect if applied to older
> kernels.

So this patch is meant to be backported to 5.18 only, right?

-- 
An old man doll... just what I always wanted! - Clara

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ