All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@kernel.org>
To: Vignesh Raghavendra <vigneshr@ti.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
	Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
	Nishanth Menon <nm@ti.com>,
	Andreas Kemnade <andreas@kemnade.info>
Subject: Re: [PATCH v3] dt-bindings: i2c: Move i2c-omap.txt to YAML format
Date: Fri, 4 Jun 2021 22:29:24 +0200	[thread overview]
Message-ID: <YLqNJLK7jylURwcP@kunai> (raw)
In-Reply-To: <20210526100412.484-1-vigneshr@ti.com>

[-- Attachment #1: Type: text/plain, Size: 435 bytes --]

On Wed, May 26, 2021 at 03:34:12PM +0530, Vignesh Raghavendra wrote:
> Convert i2c-omap.txt to YAML schema for better checks and documentation.
> 
> Following properties were used in DT but were not documented in txt
> bindings and has been included in YAML schema:
> 1. Include ti,am4372-i2c compatible
> 2. Document clocks property
> 
> Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>

Applied to for-next, thanks!


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@kernel.org>
To: Vignesh Raghavendra <vigneshr@ti.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
	Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
	Nishanth Menon <nm@ti.com>,
	Andreas Kemnade <andreas@kemnade.info>
Subject: Re: [PATCH v3] dt-bindings: i2c: Move i2c-omap.txt to YAML format
Date: Fri, 4 Jun 2021 22:29:24 +0200	[thread overview]
Message-ID: <YLqNJLK7jylURwcP@kunai> (raw)
In-Reply-To: <20210526100412.484-1-vigneshr@ti.com>


[-- Attachment #1.1: Type: text/plain, Size: 435 bytes --]

On Wed, May 26, 2021 at 03:34:12PM +0530, Vignesh Raghavendra wrote:
> Convert i2c-omap.txt to YAML schema for better checks and documentation.
> 
> Following properties were used in DT but were not documented in txt
> bindings and has been included in YAML schema:
> 1. Include ti,am4372-i2c compatible
> 2. Document clocks property
> 
> Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>

Applied to for-next, thanks!


[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2021-06-04 20:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-26 10:04 [PATCH v3] dt-bindings: i2c: Move i2c-omap.txt to YAML format Vignesh Raghavendra
2021-05-26 10:04 ` Vignesh Raghavendra
2021-06-02 19:06 ` Rob Herring
2021-06-02 19:06   ` Rob Herring
2021-06-04 20:29 ` Wolfram Sang [this message]
2021-06-04 20:29   ` 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=YLqNJLK7jylURwcP@kunai \
    --to=wsa@kernel.org \
    --cc=andreas@kemnade.info \
    --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=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=vigneshr@ti.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.