Searched hist:"8548 a63b37be4891e7972ba058b785d9468e8907" (Results 1 – 6 of 6) sorted by relevance
/linux/drivers/iio/buffer/ |
H A D | Kconfig | 8548a63b37be4891e7972ba058b785d9468e8907 Fri Aug 14 16:54:55 CEST 2015 Lars-Peter Clausen <lars@metafoo.de> iio: Move generic buffer implementations to sub-directory
For generic IIO trigger implementations we already have a sub-directory, but the generic buffer implementations currently reside in the IIO top-level directory. The main reason is that things have historically grown into this form.
With more generic buffer implementations on its way now is the perfect time to clean this up and introduce a sub-directory for generic buffer implementations to avoid too much clutter in the top-level directory.
Signed-off-by: Lars-Peter Clausen <lars@metafoo.de> Signed-off-by: Jonathan Cameron <jic23@kernel.org>
|
H A D | Makefile | 8548a63b37be4891e7972ba058b785d9468e8907 Fri Aug 14 16:54:55 CEST 2015 Lars-Peter Clausen <lars@metafoo.de> iio: Move generic buffer implementations to sub-directory
For generic IIO trigger implementations we already have a sub-directory, but the generic buffer implementations currently reside in the IIO top-level directory. The main reason is that things have historically grown into this form.
With more generic buffer implementations on its way now is the perfect time to clean this up and introduce a sub-directory for generic buffer implementations to avoid too much clutter in the top-level directory.
Signed-off-by: Lars-Peter Clausen <lars@metafoo.de> Signed-off-by: Jonathan Cameron <jic23@kernel.org>
|
H A D | industrialio-buffer-cb.c | 8548a63b37be4891e7972ba058b785d9468e8907 Fri Aug 14 16:54:55 CEST 2015 Lars-Peter Clausen <lars@metafoo.de> iio: Move generic buffer implementations to sub-directory
For generic IIO trigger implementations we already have a sub-directory, but the generic buffer implementations currently reside in the IIO top-level directory. The main reason is that things have historically grown into this form.
With more generic buffer implementations on its way now is the perfect time to clean this up and introduce a sub-directory for generic buffer implementations to avoid too much clutter in the top-level directory.
Signed-off-by: Lars-Peter Clausen <lars@metafoo.de> Signed-off-by: Jonathan Cameron <jic23@kernel.org>
|
H A D | industrialio-triggered-buffer.c | 8548a63b37be4891e7972ba058b785d9468e8907 Fri Aug 14 16:54:55 CEST 2015 Lars-Peter Clausen <lars@metafoo.de> iio: Move generic buffer implementations to sub-directory
For generic IIO trigger implementations we already have a sub-directory, but the generic buffer implementations currently reside in the IIO top-level directory. The main reason is that things have historically grown into this form.
With more generic buffer implementations on its way now is the perfect time to clean this up and introduce a sub-directory for generic buffer implementations to avoid too much clutter in the top-level directory.
Signed-off-by: Lars-Peter Clausen <lars@metafoo.de> Signed-off-by: Jonathan Cameron <jic23@kernel.org>
|
H A D | kfifo_buf.c | 8548a63b37be4891e7972ba058b785d9468e8907 Fri Aug 14 16:54:55 CEST 2015 Lars-Peter Clausen <lars@metafoo.de> iio: Move generic buffer implementations to sub-directory
For generic IIO trigger implementations we already have a sub-directory, but the generic buffer implementations currently reside in the IIO top-level directory. The main reason is that things have historically grown into this form.
With more generic buffer implementations on its way now is the perfect time to clean this up and introduce a sub-directory for generic buffer implementations to avoid too much clutter in the top-level directory.
Signed-off-by: Lars-Peter Clausen <lars@metafoo.de> Signed-off-by: Jonathan Cameron <jic23@kernel.org>
|
/linux/drivers/iio/ |
H A D | Kconfig | diff 8548a63b37be4891e7972ba058b785d9468e8907 Fri Aug 14 16:54:55 CEST 2015 Lars-Peter Clausen <lars@metafoo.de> iio: Move generic buffer implementations to sub-directory
For generic IIO trigger implementations we already have a sub-directory, but the generic buffer implementations currently reside in the IIO top-level directory. The main reason is that things have historically grown into this form.
With more generic buffer implementations on its way now is the perfect time to clean this up and introduce a sub-directory for generic buffer implementations to avoid too much clutter in the top-level directory.
Signed-off-by: Lars-Peter Clausen <lars@metafoo.de> Signed-off-by: Jonathan Cameron <jic23@kernel.org>
|