| /freebsd/sys/dev/gpio/ |
| H A D | gpioled_fdt.c | diff 217d17bcd3f525fbdf124cfbc926f8033da69805 Mon Apr 09 00:59:34 CEST 2018 Oleksandr Tymoshenko <gonzo@FreeBSD.org> Clean up OF_getprop_alloc API
OF_getprop_alloc takes element size argument and returns number of
elements in the property. There are valid use cases for such behavior
but mostly API consumers pass 1 as element size to get string
properties. What API users would expect from OF_getprop_alloc is to be
a combination of malloc + OF_getprop with the same semantic of return
value. This patch modifies API signature to match these expectations.
For the valid use cases with element size != 1 and to reduce
modification scope new OF_getprop_alloc_multi function has been
introduced that behaves the same way OF_getprop_alloc behaved prior to
this patch.
Reviewed by: ian, manu
Differential Revision: https://reviews.freebsd.org/D14850
|
| H A D | gpiokeys.c | diff 217d17bcd3f525fbdf124cfbc926f8033da69805 Mon Apr 09 00:59:34 CEST 2018 Oleksandr Tymoshenko <gonzo@FreeBSD.org> Clean up OF_getprop_alloc API
OF_getprop_alloc takes element size argument and returns number of
elements in the property. There are valid use cases for such behavior
but mostly API consumers pass 1 as element size to get string
properties. What API users would expect from OF_getprop_alloc is to be
a combination of malloc + OF_getprop with the same semantic of return
value. This patch modifies API signature to match these expectations.
For the valid use cases with element size != 1 and to reduce
modification scope new OF_getprop_alloc_multi function has been
introduced that behaves the same way OF_getprop_alloc behaved prior to
this patch.
Reviewed by: ian, manu
Differential Revision: https://reviews.freebsd.org/D14850
|
| /freebsd/sys/arm/nvidia/ |
| H A D | tegra_pinmux.c | diff 217d17bcd3f525fbdf124cfbc926f8033da69805 Mon Apr 09 00:59:34 CEST 2018 Oleksandr Tymoshenko <gonzo@FreeBSD.org> Clean up OF_getprop_alloc API
OF_getprop_alloc takes element size argument and returns number of
elements in the property. There are valid use cases for such behavior
but mostly API consumers pass 1 as element size to get string
properties. What API users would expect from OF_getprop_alloc is to be
a combination of malloc + OF_getprop with the same semantic of return
value. This patch modifies API signature to match these expectations.
For the valid use cases with element size != 1 and to reduce
modification scope new OF_getprop_alloc_multi function has been
introduced that behaves the same way OF_getprop_alloc behaved prior to
this patch.
Reviewed by: ian, manu
Differential Revision: https://reviews.freebsd.org/D14850
|
| H A D | as3722_gpio.c | diff 217d17bcd3f525fbdf124cfbc926f8033da69805 Mon Apr 09 00:59:34 CEST 2018 Oleksandr Tymoshenko <gonzo@FreeBSD.org> Clean up OF_getprop_alloc API
OF_getprop_alloc takes element size argument and returns number of
elements in the property. There are valid use cases for such behavior
but mostly API consumers pass 1 as element size to get string
properties. What API users would expect from OF_getprop_alloc is to be
a combination of malloc + OF_getprop with the same semantic of return
value. This patch modifies API signature to match these expectations.
For the valid use cases with element size != 1 and to reduce
modification scope new OF_getprop_alloc_multi function has been
introduced that behaves the same way OF_getprop_alloc behaved prior to
this patch.
Reviewed by: ian, manu
Differential Revision: https://reviews.freebsd.org/D14850
|
| H A D | as3722_regulators.c | diff 217d17bcd3f525fbdf124cfbc926f8033da69805 Mon Apr 09 00:59:34 CEST 2018 Oleksandr Tymoshenko <gonzo@FreeBSD.org> Clean up OF_getprop_alloc API
OF_getprop_alloc takes element size argument and returns number of
elements in the property. There are valid use cases for such behavior
but mostly API consumers pass 1 as element size to get string
properties. What API users would expect from OF_getprop_alloc is to be
a combination of malloc + OF_getprop with the same semantic of return
value. This patch modifies API signature to match these expectations.
For the valid use cases with element size != 1 and to reduce
modification scope new OF_getprop_alloc_multi function has been
introduced that behaves the same way OF_getprop_alloc behaved prior to
this patch.
Reviewed by: ian, manu
Differential Revision: https://reviews.freebsd.org/D14850
|
| H A D | tegra_usbphy.c | diff 217d17bcd3f525fbdf124cfbc926f8033da69805 Mon Apr 09 00:59:34 CEST 2018 Oleksandr Tymoshenko <gonzo@FreeBSD.org> Clean up OF_getprop_alloc API
OF_getprop_alloc takes element size argument and returns number of
elements in the property. There are valid use cases for such behavior
but mostly API consumers pass 1 as element size to get string
properties. What API users would expect from OF_getprop_alloc is to be
a combination of malloc + OF_getprop with the same semantic of return
value. This patch modifies API signature to match these expectations.
For the valid use cases with element size != 1 and to reduce
modification scope new OF_getprop_alloc_multi function has been
introduced that behaves the same way OF_getprop_alloc behaved prior to
this patch.
Reviewed by: ian, manu
Differential Revision: https://reviews.freebsd.org/D14850
|
| /freebsd/sys/arm/ti/usb/ |
| H A D | omap_host.c | diff 217d17bcd3f525fbdf124cfbc926f8033da69805 Mon Apr 09 00:59:34 CEST 2018 Oleksandr Tymoshenko <gonzo@FreeBSD.org> Clean up OF_getprop_alloc API
OF_getprop_alloc takes element size argument and returns number of
elements in the property. There are valid use cases for such behavior
but mostly API consumers pass 1 as element size to get string
properties. What API users would expect from OF_getprop_alloc is to be
a combination of malloc + OF_getprop with the same semantic of return
value. This patch modifies API signature to match these expectations.
For the valid use cases with element size != 1 and to reduce
modification scope new OF_getprop_alloc_multi function has been
introduced that behaves the same way OF_getprop_alloc behaved prior to
this patch.
Reviewed by: ian, manu
Differential Revision: https://reviews.freebsd.org/D14850
|
| /freebsd/sys/dev/neta/ |
| H A D | if_mvneta_fdt.c | diff 217d17bcd3f525fbdf124cfbc926f8033da69805 Mon Apr 09 00:59:34 CEST 2018 Oleksandr Tymoshenko <gonzo@FreeBSD.org> Clean up OF_getprop_alloc API
OF_getprop_alloc takes element size argument and returns number of
elements in the property. There are valid use cases for such behavior
but mostly API consumers pass 1 as element size to get string
properties. What API users would expect from OF_getprop_alloc is to be
a combination of malloc + OF_getprop with the same semantic of return
value. This patch modifies API signature to match these expectations.
For the valid use cases with element size != 1 and to reduce
modification scope new OF_getprop_alloc_multi function has been
introduced that behaves the same way OF_getprop_alloc behaved prior to
this patch.
Reviewed by: ian, manu
Differential Revision: https://reviews.freebsd.org/D14850
|
| /freebsd/sys/dev/usb/controller/ |
| H A D | ehci_fsl.c | diff 217d17bcd3f525fbdf124cfbc926f8033da69805 Mon Apr 09 00:59:34 CEST 2018 Oleksandr Tymoshenko <gonzo@FreeBSD.org> Clean up OF_getprop_alloc API
OF_getprop_alloc takes element size argument and returns number of
elements in the property. There are valid use cases for such behavior
but mostly API consumers pass 1 as element size to get string
properties. What API users would expect from OF_getprop_alloc is to be
a combination of malloc + OF_getprop with the same semantic of return
value. This patch modifies API signature to match these expectations.
For the valid use cases with element size != 1 and to reduce
modification scope new OF_getprop_alloc_multi function has been
introduced that behaves the same way OF_getprop_alloc behaved prior to
this patch.
Reviewed by: ian, manu
Differential Revision: https://reviews.freebsd.org/D14850
|
| /freebsd/sys/dev/fdt/ |
| H A D | fdt_pinctrl.c | diff 217d17bcd3f525fbdf124cfbc926f8033da69805 Mon Apr 09 00:59:34 CEST 2018 Oleksandr Tymoshenko <gonzo@FreeBSD.org> Clean up OF_getprop_alloc API
OF_getprop_alloc takes element size argument and returns number of
elements in the property. There are valid use cases for such behavior
but mostly API consumers pass 1 as element size to get string
properties. What API users would expect from OF_getprop_alloc is to be
a combination of malloc + OF_getprop with the same semantic of return
value. This patch modifies API signature to match these expectations.
For the valid use cases with element size != 1 and to reduce
modification scope new OF_getprop_alloc_multi function has been
introduced that behaves the same way OF_getprop_alloc behaved prior to
this patch.
Reviewed by: ian, manu
Differential Revision: https://reviews.freebsd.org/D14850
|
| H A D | fdt_slicer.c | diff 217d17bcd3f525fbdf124cfbc926f8033da69805 Mon Apr 09 00:59:34 CEST 2018 Oleksandr Tymoshenko <gonzo@FreeBSD.org> Clean up OF_getprop_alloc API
OF_getprop_alloc takes element size argument and returns number of
elements in the property. There are valid use cases for such behavior
but mostly API consumers pass 1 as element size to get string
properties. What API users would expect from OF_getprop_alloc is to be
a combination of malloc + OF_getprop with the same semantic of return
value. This patch modifies API signature to match these expectations.
For the valid use cases with element size != 1 and to reduce
modification scope new OF_getprop_alloc_multi function has been
introduced that behaves the same way OF_getprop_alloc behaved prior to
this patch.
Reviewed by: ian, manu
Differential Revision: https://reviews.freebsd.org/D14850
|
| /freebsd/sys/powerpc/mpc85xx/ |
| H A D | fsl_diu.c | diff 217d17bcd3f525fbdf124cfbc926f8033da69805 Mon Apr 09 00:59:34 CEST 2018 Oleksandr Tymoshenko <gonzo@FreeBSD.org> Clean up OF_getprop_alloc API
OF_getprop_alloc takes element size argument and returns number of
elements in the property. There are valid use cases for such behavior
but mostly API consumers pass 1 as element size to get string
properties. What API users would expect from OF_getprop_alloc is to be
a combination of malloc + OF_getprop with the same semantic of return
value. This patch modifies API signature to match these expectations.
For the valid use cases with element size != 1 and to reduce
modification scope new OF_getprop_alloc_multi function has been
introduced that behaves the same way OF_getprop_alloc behaved prior to
this patch.
Reviewed by: ian, manu
Differential Revision: https://reviews.freebsd.org/D14850
|
| /freebsd/sys/arm/allwinner/ |
| H A D | aw_gpio.c | diff 217d17bcd3f525fbdf124cfbc926f8033da69805 Mon Apr 09 00:59:34 CEST 2018 Oleksandr Tymoshenko <gonzo@FreeBSD.org> Clean up OF_getprop_alloc API
OF_getprop_alloc takes element size argument and returns number of
elements in the property. There are valid use cases for such behavior
but mostly API consumers pass 1 as element size to get string
properties. What API users would expect from OF_getprop_alloc is to be
a combination of malloc + OF_getprop with the same semantic of return
value. This patch modifies API signature to match these expectations.
For the valid use cases with element size != 1 and to reduce
modification scope new OF_getprop_alloc_multi function has been
introduced that behaves the same way OF_getprop_alloc behaved prior to
this patch.
Reviewed by: ian, manu
Differential Revision: https://reviews.freebsd.org/D14850
|
| H A D | if_awg.c | diff 217d17bcd3f525fbdf124cfbc926f8033da69805 Mon Apr 09 00:59:34 CEST 2018 Oleksandr Tymoshenko <gonzo@FreeBSD.org> Clean up OF_getprop_alloc API
OF_getprop_alloc takes element size argument and returns number of
elements in the property. There are valid use cases for such behavior
but mostly API consumers pass 1 as element size to get string
properties. What API users would expect from OF_getprop_alloc is to be
a combination of malloc + OF_getprop with the same semantic of return
value. This patch modifies API signature to match these expectations.
For the valid use cases with element size != 1 and to reduce
modification scope new OF_getprop_alloc_multi function has been
introduced that behaves the same way OF_getprop_alloc behaved prior to
this patch.
Reviewed by: ian, manu
Differential Revision: https://reviews.freebsd.org/D14850
|
| /freebsd/sys/arm/nvidia/tegra124/ |
| H A D | tegra124_xusbpadctl.c | diff 217d17bcd3f525fbdf124cfbc926f8033da69805 Mon Apr 09 00:59:34 CEST 2018 Oleksandr Tymoshenko <gonzo@FreeBSD.org> Clean up OF_getprop_alloc API
OF_getprop_alloc takes element size argument and returns number of
elements in the property. There are valid use cases for such behavior
but mostly API consumers pass 1 as element size to get string
properties. What API users would expect from OF_getprop_alloc is to be
a combination of malloc + OF_getprop with the same semantic of return
value. This patch modifies API signature to match these expectations.
For the valid use cases with element size != 1 and to reduce
modification scope new OF_getprop_alloc_multi function has been
introduced that behaves the same way OF_getprop_alloc behaved prior to
this patch.
Reviewed by: ian, manu
Differential Revision: https://reviews.freebsd.org/D14850
|
| /freebsd/sys/arm/freescale/vybrid/ |
| H A D | vf_ccm.c | diff 217d17bcd3f525fbdf124cfbc926f8033da69805 Mon Apr 09 00:59:34 CEST 2018 Oleksandr Tymoshenko <gonzo@FreeBSD.org> Clean up OF_getprop_alloc API
OF_getprop_alloc takes element size argument and returns number of
elements in the property. There are valid use cases for such behavior
but mostly API consumers pass 1 as element size to get string
properties. What API users would expect from OF_getprop_alloc is to be
a combination of malloc + OF_getprop with the same semantic of return
value. This patch modifies API signature to match these expectations.
For the valid use cases with element size != 1 and to reduce
modification scope new OF_getprop_alloc_multi function has been
introduced that behaves the same way OF_getprop_alloc behaved prior to
this patch.
Reviewed by: ian, manu
Differential Revision: https://reviews.freebsd.org/D14850
|
| /freebsd/sys/dev/altera/avgen/ |
| H A D | altera_avgen_fdt.c | diff 217d17bcd3f525fbdf124cfbc926f8033da69805 Mon Apr 09 00:59:34 CEST 2018 Oleksandr Tymoshenko <gonzo@FreeBSD.org> Clean up OF_getprop_alloc API
OF_getprop_alloc takes element size argument and returns number of
elements in the property. There are valid use cases for such behavior
but mostly API consumers pass 1 as element size to get string
properties. What API users would expect from OF_getprop_alloc is to be
a combination of malloc + OF_getprop with the same semantic of return
value. This patch modifies API signature to match these expectations.
For the valid use cases with element size != 1 and to reduce
modification scope new OF_getprop_alloc_multi function has been
introduced that behaves the same way OF_getprop_alloc behaved prior to
this patch.
Reviewed by: ian, manu
Differential Revision: https://reviews.freebsd.org/D14850
|
| /freebsd/sys/dev/vnic/ |
| H A D | thunder_bgx_fdt.c | diff 217d17bcd3f525fbdf124cfbc926f8033da69805 Mon Apr 09 00:59:34 CEST 2018 Oleksandr Tymoshenko <gonzo@FreeBSD.org> Clean up OF_getprop_alloc API
OF_getprop_alloc takes element size argument and returns number of
elements in the property. There are valid use cases for such behavior
but mostly API consumers pass 1 as element size to get string
properties. What API users would expect from OF_getprop_alloc is to be
a combination of malloc + OF_getprop with the same semantic of return
value. This patch modifies API signature to match these expectations.
For the valid use cases with element size != 1 and to reduce
modification scope new OF_getprop_alloc_multi function has been
introduced that behaves the same way OF_getprop_alloc behaved prior to
this patch.
Reviewed by: ian, manu
Differential Revision: https://reviews.freebsd.org/D14850
|
| /freebsd/sys/powerpc/psim/ |
| H A D | iobus.c | diff 217d17bcd3f525fbdf124cfbc926f8033da69805 Mon Apr 09 00:59:34 CEST 2018 Oleksandr Tymoshenko <gonzo@FreeBSD.org> Clean up OF_getprop_alloc API
OF_getprop_alloc takes element size argument and returns number of
elements in the property. There are valid use cases for such behavior
but mostly API consumers pass 1 as element size to get string
properties. What API users would expect from OF_getprop_alloc is to be
a combination of malloc + OF_getprop with the same semantic of return
value. This patch modifies API signature to match these expectations.
For the valid use cases with element size != 1 and to reduce
modification scope new OF_getprop_alloc_multi function has been
introduced that behaves the same way OF_getprop_alloc behaved prior to
this patch.
Reviewed by: ian, manu
Differential Revision: https://reviews.freebsd.org/D14850
|
| /freebsd/sys/dev/etherswitch/e6000sw/ |
| H A D | e6000sw.c | diff 217d17bcd3f525fbdf124cfbc926f8033da69805 Mon Apr 09 00:59:34 CEST 2018 Oleksandr Tymoshenko <gonzo@FreeBSD.org> Clean up OF_getprop_alloc API
OF_getprop_alloc takes element size argument and returns number of
elements in the property. There are valid use cases for such behavior
but mostly API consumers pass 1 as element size to get string
properties. What API users would expect from OF_getprop_alloc is to be
a combination of malloc + OF_getprop with the same semantic of return
value. This patch modifies API signature to match these expectations.
For the valid use cases with element size != 1 and to reduce
modification scope new OF_getprop_alloc_multi function has been
introduced that behaves the same way OF_getprop_alloc behaved prior to
this patch.
Reviewed by: ian, manu
Differential Revision: https://reviews.freebsd.org/D14850
|
| /freebsd/sys/arm/broadcom/bcm2835/ |
| H A D | bcm2835_gpio.c | diff 217d17bcd3f525fbdf124cfbc926f8033da69805 Mon Apr 09 00:59:34 CEST 2018 Oleksandr Tymoshenko <gonzo@FreeBSD.org> Clean up OF_getprop_alloc API
OF_getprop_alloc takes element size argument and returns number of
elements in the property. There are valid use cases for such behavior
but mostly API consumers pass 1 as element size to get string
properties. What API users would expect from OF_getprop_alloc is to be
a combination of malloc + OF_getprop with the same semantic of return
value. This patch modifies API signature to match these expectations.
For the valid use cases with element size != 1 and to reduce
modification scope new OF_getprop_alloc_multi function has been
introduced that behaves the same way OF_getprop_alloc behaved prior to
this patch.
Reviewed by: ian, manu
Differential Revision: https://reviews.freebsd.org/D14850
|
| /freebsd/sys/dev/ofw/ |
| H A D | openfirm.h | diff 217d17bcd3f525fbdf124cfbc926f8033da69805 Mon Apr 09 00:59:34 CEST 2018 Oleksandr Tymoshenko <gonzo@FreeBSD.org> Clean up OF_getprop_alloc API
OF_getprop_alloc takes element size argument and returns number of
elements in the property. There are valid use cases for such behavior
but mostly API consumers pass 1 as element size to get string
properties. What API users would expect from OF_getprop_alloc is to be
a combination of malloc + OF_getprop with the same semantic of return
value. This patch modifies API signature to match these expectations.
For the valid use cases with element size != 1 and to reduce
modification scope new OF_getprop_alloc_multi function has been
introduced that behaves the same way OF_getprop_alloc behaved prior to
this patch.
Reviewed by: ian, manu
Differential Revision: https://reviews.freebsd.org/D14850
|
| H A D | openfirm.c | diff 217d17bcd3f525fbdf124cfbc926f8033da69805 Mon Apr 09 00:59:34 CEST 2018 Oleksandr Tymoshenko <gonzo@FreeBSD.org> Clean up OF_getprop_alloc API
OF_getprop_alloc takes element size argument and returns number of
elements in the property. There are valid use cases for such behavior
but mostly API consumers pass 1 as element size to get string
properties. What API users would expect from OF_getprop_alloc is to be
a combination of malloc + OF_getprop with the same semantic of return
value. This patch modifies API signature to match these expectations.
For the valid use cases with element size != 1 and to reduce
modification scope new OF_getprop_alloc_multi function has been
introduced that behaves the same way OF_getprop_alloc behaved prior to
this patch.
Reviewed by: ian, manu
Differential Revision: https://reviews.freebsd.org/D14850
|
| H A D | ofw_bus_subr.c | diff 217d17bcd3f525fbdf124cfbc926f8033da69805 Mon Apr 09 00:59:34 CEST 2018 Oleksandr Tymoshenko <gonzo@FreeBSD.org> Clean up OF_getprop_alloc API
OF_getprop_alloc takes element size argument and returns number of
elements in the property. There are valid use cases for such behavior
but mostly API consumers pass 1 as element size to get string
properties. What API users would expect from OF_getprop_alloc is to be
a combination of malloc + OF_getprop with the same semantic of return
value. This patch modifies API signature to match these expectations.
For the valid use cases with element size != 1 and to reduce
modification scope new OF_getprop_alloc_multi function has been
introduced that behaves the same way OF_getprop_alloc behaved prior to
this patch.
Reviewed by: ian, manu
Differential Revision: https://reviews.freebsd.org/D14850
|
| /freebsd/sys/powerpc/powermac/ |
| H A D | uninorth.c | diff 217d17bcd3f525fbdf124cfbc926f8033da69805 Mon Apr 09 00:59:34 CEST 2018 Oleksandr Tymoshenko <gonzo@FreeBSD.org> Clean up OF_getprop_alloc API
OF_getprop_alloc takes element size argument and returns number of
elements in the property. There are valid use cases for such behavior
but mostly API consumers pass 1 as element size to get string
properties. What API users would expect from OF_getprop_alloc is to be
a combination of malloc + OF_getprop with the same semantic of return
value. This patch modifies API signature to match these expectations.
For the valid use cases with element size != 1 and to reduce
modification scope new OF_getprop_alloc_multi function has been
introduced that behaves the same way OF_getprop_alloc behaved prior to
this patch.
Reviewed by: ian, manu
Differential Revision: https://reviews.freebsd.org/D14850
|