| 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
| ||
|
Date: Fri, 30 May 2014 20:25:16 +0100 From: Lee Jones <lee.jones@...aro.org> To: Wolfram Sang <wsa@...-dreams.de> Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, grant.likely@...aro.org, linus.walleij@...aro.org, linux-i2c@...r.kernel.org Subject: Re: [PATCH] i2c: Make I2C ID tables non-mandatory for DT'ed and/or ACPI'ed devices > > Would you mind telling me what I have changed that affects drivers > > registering via Sysfs? > > Check Documentation/i2c/instantiating-devices, method 4. If a driver > does not have i2c_device_id, then this method won't work because the > newly created device has no of_node or ACPI_node and nothing will match. > Looking at the bigger picture, I'd really like to keep this feature. > People use it. Right, I read the function which provides the functionality, but my point is; I don't think my patch changes the semantics in a way which would adversely affect this option. If you think that it does, can you specify how please? Does the sysfs method create a i2c_device_id table? If not, how does it probe successfully pre-patch? -- Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists