From: Ludovic Desroches <ludovic.desroches@microchip.com>
To: Eugen Hristev - M18282 <Eugen.Hristev@microchip.com>
Cc: "robh+dt@kernel.org" <robh+dt@kernel.org>,
"wsa@the-dreams.de" <wsa@the-dreams.de>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"peda@axentia.se" <peda@axentia.se>,
"Codrin Ciubotariu - M19940" <Codrin.Ciubotariu@microchip.com>,
Nicolas Ferre - M43238 <Nicolas.Ferre@microchip.com>
Subject: Re: [PATCH 1/3] dt-bindings: i2c: at91: cosmetic formatting of compatible list
Date: Tue, 3 Dec 2019 07:57:51 +0100 [thread overview]
Message-ID: <20191203065751.fgwwko3e63antodb@M43218.corp.atmel.com> (raw)
In-Reply-To: <1575276957-5615-1-git-send-email-eugen.hristev@microchip.com>
On Mon, Dec 02, 2019 at 09:56:35AM +0100, Eugen Hristev - M18282 wrote:
> From: Eugen Hristev <eugen.hristev@microchip.com>
>
> Format the list of compatibles with one compatible per line.
>
> Suggested-by: Peter Rosin <peda@axentia.se>
> Signed-off-by: Eugen Hristev <eugen.hristev@microchip.com>
Acked-by: Ludovic Desroches <ludovic.desroches@microchip.com>
Thanks
> ---
> Documentation/devicetree/bindings/i2c/i2c-at91.txt | 14 ++++++++++----
> 1 file changed, 10 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/i2c/i2c-at91.txt b/Documentation/devicetree/bindings/i2c/i2c-at91.txt
> index 2210f43..d35cd63 100644
> --- a/Documentation/devicetree/bindings/i2c/i2c-at91.txt
> +++ b/Documentation/devicetree/bindings/i2c/i2c-at91.txt
> @@ -1,10 +1,16 @@
> I2C for Atmel platforms
>
> Required properties :
> -- compatible : Must be "atmel,at91rm9200-i2c", "atmel,at91sam9261-i2c",
> - "atmel,at91sam9260-i2c", "atmel,at91sam9g20-i2c", "atmel,at91sam9g10-i2c",
> - "atmel,at91sam9x5-i2c", "atmel,sama5d4-i2c", "atmel,sama5d2-i2c" or
> - "microchip,sam9x60-i2c"
> +- compatible : Must be one of:
> + "atmel,at91rm9200-i2c",
> + "atmel,at91sam9261-i2c",
> + "atmel,at91sam9260-i2c",
> + "atmel,at91sam9g20-i2c",
> + "atmel,at91sam9g10-i2c",
> + "atmel,at91sam9x5-i2c",
> + "atmel,sama5d4-i2c",
> + "atmel,sama5d2-i2c",
> + "microchip,sam9x60-i2c".
> - reg: physical base address of the controller and length of memory mapped
> region.
> - interrupts: interrupt number to the cpu.
> --
> 2.7.4
>
prev parent reply other threads:[~2019-12-03 6:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 8:56 [PATCH 1/3] dt-bindings: i2c: at91: cosmetic formatting of compatible list Eugen.Hristev
2019-12-02 8:56 ` [PATCH 2/3] i2c: at91: fix clk_offset for sama5d2 Eugen.Hristev
2019-12-02 9:01 ` [PATCH v2 2/3] i2c: at91: fix clk_offset for sam9x60 Eugen.Hristev
2019-12-03 7:01 ` Ludovic Desroches
2019-12-06 16:58 ` [PATCH 2/3] i2c: at91: fix clk_offset for sama5d2 Codrin.Ciubotariu
2019-12-02 8:56 ` [PATCH 3/3] i2c: at91: remote default value initialization Eugen.Hristev
2019-12-03 7:13 ` Ludovic Desroches
2019-12-03 6:57 ` Ludovic Desroches [this message]
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=20191203065751.fgwwko3e63antodb@M43218.corp.atmel.com \
--to=ludovic.desroches@microchip.com \
--cc=Codrin.Ciubotariu@microchip.com \
--cc=Eugen.Hristev@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=robh+dt@kernel.org \
--cc=wsa@the-dreams.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;
as well as URLs for NNTP newsgroup(s).