[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180907103407.GA2310@kunai>
Date: Fri, 7 Sep 2018 12:34:07 +0200
From: Wolfram Sang <wsa@...-dreams.de>
To: Michal Simek <michal.simek@...inx.com>
Cc: linux-kernel@...r.kernel.org, monstr@...str.eu,
linux-i2c@...r.kernel.org, "David S. Miller" <davem@...emloft.net>,
Heiko Schocher <hs@...x.de>,
Mauro Carvalho Chehab <mchehab+samsung@...nel.org>,
u-boot@...ts.denx.de, Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] i2c: xiic: Record xilinx i2c with Zynq fragment
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@...inx.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@....com>
> --
> 1.9.1
>
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists