From: Wolfram Sang <wsa@the-dreams.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] i2c: xiic: Record xilinx i2c with Zynq fragment
Date: Fri, 7 Sep 2018 12:34:07 +0200 [thread overview]
Message-ID: <20180907103407.GA2310@kunai> (raw)
In-Reply-To: <a36257084b0816bd84bb1caacdcde586b7fcb007.1536300108.git.michal.simek@xilinx.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
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180907/e0470de4/attachment.sig>
next prev parent reply other threads:[~2018-09-07 10:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 6:02 [U-Boot] [PATCH] i2c: xiic: Record xilinx i2c with Zynq fragment Michal Simek
2018-09-07 10:34 ` Wolfram Sang [this message]
2018-09-07 10:57 ` Michal Simek
2018-09-07 11:17 ` Wolfram Sang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180907103407.GA2310@kunai \
--to=wsa@the-dreams.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox