Guys,
Any additional comments?
Or the patch is ready to be merged?
Thanks,
--- Kosta Z.
This change increases the source code readability.
Instead of using `spi->child[cs].direct_access.XXX` use `dir_acc->XXX`.
Instead of using `orion_spi->child[cs].direct_access.vaddr` use `vaddr`.
Signed-off-by: Kosta Zertsekel
Reviewed-by: Andrew Lunn
Reviewed-by: Stefan Roese
---
dr
This change increases the source code readability.
Instead of using `spi->child[cs].direct_access.XXX` use `dir_acc->XXX`.
Instead of using `orion_spi->child[cs].direct_access.vaddr` use `vaddr`.
Signed-off-by: Kosta Zertsekel
Reviewed-by: Andrew Lunn
---
drivers/spi/spi-ori
This change increases the source code readability.
Instead of using `spi->child[cs].direct_access.XXX` use `dir_acc->XXX`.
Instead of using `orion_spi->child[cs].direct_access.vaddr` use `vaddr`.
Signed-off-by: Kosta Zertsekel
---
drivers/spi/spi-orion.c | 22 +++--
This change increases the source code readability.
Instead of using `spi->child[cs].direct_access.XXX` use `dacc->XXX`.
Instead of using `orion_spi->child[cs].direct_access.vaddr` use `vaddr`.
Signed-off-by: Kosta Zertsekel
---
drivers/spi/spi-orion.c | 22 +++---
1 fil
This change increases the source code readability.
Instead of using `spi->child[cs].direct_access.XXX` use `dacc->XXX`.
Instead of using `orion_spi->child[cs].direct_access.vaddr` use `vaddr`.
Signed-off-by: Kosta Zertsekel
---
drivers/spi/spi-orion.c | 22 +++---
1 fil
On Mon, Aug 6, 2018 at 10:09 PM Andrew Lunn wrote:
>> @@ -683,6 +683,7 @@ static int orion_spi_probe(struct platform_device *pdev)
>>
>> /* Scan all SPI devices of this controller for direct mapped devices */
>> for_each_available_child_of_node(pdev->dev.of_node, np) {
>> +
This change increases the source code readability.
Instead of using `spi->child[cs].direct_access.XXX` use `dacc->XXX`.
Instead of using `orion_spi->child[cs].direct_access.vaddr` use `vaddr`.
Signed-off-by: Kosta Zertsekel
---
drivers/spi/spi-orion.c | 22 +++---
1 fil
Hi guys,
The question
--
What are the possible drawbacks of enabling CONFIG_HOTPLUG_CPU for CPU
that does not have hardware support for hot-plug?
The question I'd like to ask is architecture agnostic, but the described
behavior
is observed on MPCore Cortex-A9 CPU with Lin
9 matches
Mail list logo