[U-Boot] [PATCH] i2c: xiic: Record xilinx i2c with Zynq fragment
Include xilinx soft i2c controller to Zynq fragment to make clear who is responsible for it.
Signed-off-by: Michal Simek michal.simek@xilinx.com ---
Normally we are handling all these drivers via one fragment to make sure that there is only one central contact. Another reason is that people are changing and their responsibility is moving time to time.
--- MAINTAINERS | 1 + 1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS index 9ad052aeac39..d870cb57c887 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -2311,6 +2311,7 @@ F: drivers/clocksource/cadence_ttc_timer.c F: drivers/i2c/busses/i2c-cadence.c F: drivers/mmc/host/sdhci-of-arasan.c F: drivers/edac/synopsys_edac.c +F: drivers/i2c/busses/i2c-xiic.c
ARM64 PORT (AARCH64 ARCHITECTURE) M: Catalin Marinas catalin.marinas@arm.com
On Fri, Sep 07, 2018 at 08:02:05AM +0200, Michal Simek wrote:
Include xilinx soft i2c controller to Zynq fragment to make clear who is responsible for it.
Signed-off-by: Michal Simek michal.simek@xilinx.com
Cool, thanks!
Normally we are handling all these drivers via one fragment to make sure that there is only one central contact. Another reason is that people are changing and their responsibility is moving time to time.
This is fine with me, but what about sorting the entries? I don't care much because it is "your" entry, yet I thought I mention it. Let me know if I should apply this as-is nonetheless.
MAINTAINERS | 1 + 1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS index 9ad052aeac39..d870cb57c887 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -2311,6 +2311,7 @@ F: drivers/clocksource/cadence_ttc_timer.c F: drivers/i2c/busses/i2c-cadence.c F: drivers/mmc/host/sdhci-of-arasan.c F: drivers/edac/synopsys_edac.c +F: drivers/i2c/busses/i2c-xiic.c
ARM64 PORT (AARCH64 ARCHITECTURE) M: Catalin Marinas catalin.marinas@arm.com -- 1.9.1
On 7.9.2018 12:34, Wolfram Sang wrote:
On Fri, Sep 07, 2018 at 08:02:05AM +0200, Michal Simek wrote:
Include xilinx soft i2c controller to Zynq fragment to make clear who is responsible for it.
Signed-off-by: Michal Simek michal.simek@xilinx.com
Cool, thanks!
Normally we are handling all these drivers via one fragment to make sure that there is only one central contact. Another reason is that people are changing and their responsibility is moving time to time.
This is fine with me, but what about sorting the entries? I don't care much because it is "your" entry, yet I thought I mention it. Let me know if I should apply this as-is nonetheless.
It is not sorted even now that's why not big deal. I can sort it later with this included.
Thanks, Michal
On Fri, Sep 07, 2018 at 08:02:05AM +0200, Michal Simek wrote:
Include xilinx soft i2c controller to Zynq fragment to make clear who is responsible for it.
Signed-off-by: Michal Simek michal.simek@xilinx.com
Applied to for-current, thanks!
participants (2)
-
Michal Simek -
Wolfram Sang