On Fri, May 19, 2017 at 6:04 PM, Gregory CLEMENT
wrote:
> There was no entry for the mvebu pinctrl drivers. As they are tightly
> linked to the SoCs and there is a lot of common code to support the
> various pinctrl of each SoCs, then add a new entry for the
On Fri, May 19, 2017 at 6:04 PM, Gregory CLEMENT
wrote:
> There was no entry for the mvebu pinctrl drivers. As they are tightly
> linked to the SoCs and there is a lot of common code to support the
> various pinctrl of each SoCs, then add a new entry for the mvebu
> maintainers.
>
> Reviewed-by:
There was no entry for the mvebu pinctrl drivers. As they are tightly
linked to the SoCs and there is a lot of common code to support the
various pinctrl of each SoCs, then add a new entry for the mvebu
maintainers.
Reviewed-by: Thomas Petazzoni
There was no entry for the mvebu pinctrl drivers. As they are tightly
linked to the SoCs and there is a lot of common code to support the
various pinctrl of each SoCs, then add a new entry for the mvebu
maintainers.
Reviewed-by: Thomas Petazzoni
Signed-off-by: Gregory CLEMENT
---
MAINTAINERS |
4 matches
Mail list logo