16afe125b5
Now that there are no more users accessing 'mlock' directly, we can move it to the iio_dev private structure. Hence, it's now explicit that new driver's should not directly use this lock. Signed-off-by: Nuno Sá <nuno.sa@analog.com> Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com> Link: https://lore.kernel.org/r/20221012151620.1725215-5-nuno.sa@analog.com Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
17 lines
454 B
Plaintext
17 lines
454 B
Plaintext
2020-02-29
|
|
|
|
Documentation
|
|
- Binding docs for devices that are obviously used via device
|
|
tree
|
|
- Yaml conversions for abandoned drivers
|
|
- ABI Documentation
|
|
- Audit driviers/iio/staging/Documentation
|
|
|
|
- Converting drivers from device tree centric to more generic
|
|
property handlers.
|
|
|
|
- Refactor old platform_data constructs from drivers and convert it
|
|
to state struct and using property handlers and readers.
|
|
|
|
Mailing list: linux-iio@vger.kernel.org
|