projects / linux-block.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 71ac69e) | patch
hwmon: (pmbus/max31827) Explain why enum chips must not start with 0
authorGuenter Roeck <linux@roeck-us.net>
Fri, 7 Jun 2024 13:32:04 +0000 (06:32 -0700)
committerGuenter Roeck <linux@roeck-us.net>
Tue, 11 Jun 2024 14:25:03 +0000 (07:25 -0700)
commit138d45d96758db803b50761297f3331c9170bc87
treeb64b32e9c0c7c91808abcf53657cf7f8d73d5508tree
parent71ac69e08947a03925cbd5f7517cba358cda1eb3commit | diff
hwmon: (pmbus/max31827) Explain why enum chips must not start with 0

If a driver calls device_get_match_data(), the .data pointer in its id
data structures must not be NULL/0 because device_get_match_data()
returns NULL if an entry is not found. Explain that in a comment to avoid
confusion why this is required in this driver but not in other drivers.

Cc: Daniel Matyas <daniel.matyas@analog.com>
Acked-by: Nuno Sa <nuno.sa@analog.com>
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
drivers/hwmon/max31827.c diff | blob | blame | history
Linux 6.x block layer and io_uring tree(s)