Searched hist:"6 af6c371" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/drivers/dma/qcom/ |
| H A D | hidma_mgmt_sys.c | 6af6c371 Thu Apr 19 09:05:39 CDT 2018 Wolfram Sang <wsa+renesas@sang-engineering.com> dmaengine: qcom: simplify getting .drvdata
We should get drvdata from struct device directly. Going via
platform_device is an unneeded step back and forth.
Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Reviewed-by: Sinan Kaya <okaya@codeaurora.org>
Signed-off-by: Vinod Koul <vkoul@kernel.org>
6af6c371 Thu Apr 19 09:05:39 CDT 2018 Wolfram Sang <wsa+renesas@sang-engineering.com> dmaengine: qcom: simplify getting .drvdata
We should get drvdata from struct device directly. Going via
platform_device is an unneeded step back and forth.
Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Reviewed-by: Sinan Kaya <okaya@codeaurora.org>
Signed-off-by: Vinod Koul <vkoul@kernel.org>
|
| H A D | hidma.c | 6af6c371 Thu Apr 19 09:05:39 CDT 2018 Wolfram Sang <wsa+renesas@sang-engineering.com> dmaengine: qcom: simplify getting .drvdata
We should get drvdata from struct device directly. Going via
platform_device is an unneeded step back and forth.
Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Reviewed-by: Sinan Kaya <okaya@codeaurora.org>
Signed-off-by: Vinod Koul <vkoul@kernel.org>
6af6c371 Thu Apr 19 09:05:39 CDT 2018 Wolfram Sang <wsa+renesas@sang-engineering.com> dmaengine: qcom: simplify getting .drvdata
We should get drvdata from struct device directly. Going via
platform_device is an unneeded step back and forth.
Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Reviewed-by: Sinan Kaya <okaya@codeaurora.org>
Signed-off-by: Vinod Koul <vkoul@kernel.org>
|