devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Vignesh R <vigneshr@ti.com>, Sekhar Nori <nsekhar@ti.com>,
	Nishanth Menon <nm@ti.com>, Peter Rosin <peda@axentia.se>,
	linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/2] dt-bindings: i2c-omap: Add new compatible for AM654 SoCs
Date: Fri, 12 Oct 2018 14:33:34 -0500	[thread overview]
Message-ID: <20181012193334.GA29966@bogus> (raw)
In-Reply-To: <20180928052557.21663-2-vigneshr@ti.com>

On Fri, 28 Sep 2018 10:55:56 +0530, Vignesh R wrote:
> AM654 SoCs have same I2C IP as OMAP SoCs. Add new compatible to
> handle AM654 SoCs. While at that reformat the existing compatible list
> for older SoCs to list one valid compatible per line.
> 
> Signed-off-by: Vignesh R <vigneshr@ti.com>
> ---
> 
> v2: Reformat compatible existing compatible list.
> 
>  Documentation/devicetree/bindings/i2c/i2c-omap.txt | 8 ++++++--
>  1 file changed, 6 insertions(+), 2 deletions(-)
> 

Reviewed-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2018-10-12 19:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-28  5:25 [PATCH v2 0/2] i2c-omap: Enable i2c-omap driver for AM654 SoCs Vignesh R
2018-09-28  5:25 ` [PATCH v2 1/2] dt-bindings: i2c-omap: Add new compatible " Vignesh R
2018-10-12 19:33   ` Rob Herring [this message]
2018-09-28  5:25 ` [PATCH v2 2/2] i2c: busses: Kconfig: Enable I2C_OMAP for ARCH_K3 Vignesh R
2018-10-20  7:53 ` [PATCH v2 0/2] i2c-omap: Enable i2c-omap driver for AM654 SoCs Vignesh R
2018-10-28 22:34   ` Wolfram Sang
2018-11-07 17:01     ` Vignesh R
2018-11-01 16:18 ` Grygorii Strashko

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=20181012193334.GA29966@bogus \
    --to=robh@kernel.org \
    --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=nm@ti.com \
    --cc=nsekhar@ti.com \
    --cc=peda@axentia.se \
    --cc=vigneshr@ti.com \
    --cc=wsa+renesas@sang-engineering.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 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).