linux-kernel - Re: drivers/hwmon/tmp513.c:163:10: error: 'const struct regmap_config' has no member named 'reg

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] [day] [month] [year] [list]

Message-ID: <4a1103b4-e8c3-484f-a52b-29517cdd39ea@roeck-us.net>
Date: Tue, 1 Oct 2024 13:32:37 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Javier Carrasco <javier.carrasco.cruz@...il.com>,
 kernel test robot <lkp@...el.com>
Cc: oe-kbuild-all@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: drivers/hwmon/tmp513.c:163:10: error: 'const struct
 regmap_config' has no member named 'reg_bits'

On 10/1/24 11:53, Javier Carrasco wrote:
[ ... ]
> 
> The bug is not in that commit, the Kconfig entry for this driver is
> missing a 'select REGMAP_I2C'. I just tested it and then it builds
> without any issues.
> 
> I can send a patch to fix that, but I would like to know what commit it
> really fixes: the one that introduced the driver as it already used
> regmap and did not include the required select? Or the one from this
> report because it triggered, even though it is not the real source of
> the issue?
> 

I have no idea why this is reported now, but the problem was introduced with
the driver, and as you have noticed I already submitted a fix.

Thanks a lot for reviewing it!

Guenter