All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vignesh R <vigneshr@ti.com>
To: Vignesh R <vigneshr@ti.com>
Cc: Rob Herring <robh+dt@kernel.org>, <linux-omap@vger.kernel.org>,
	<linux-i2c@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, Tony Lindgren <tony@atomide.com>,
	Grygorii Strashko <grygorii.strashko@ti.com>
Subject: [PATCH v4 0/3] i2c-omap: Enable i2c-omap driver for AM654 SoCs
Date: Fri, 9 Nov 2018 16:44:09 +0530	[thread overview]
Message-ID: <20181109111412.24777-1-vigneshr@ti.com> (raw)

Couple of patches to enable i2c-omap driver to be used with TI's new
AM654 platforms.

v4:
Add maintainer tag instead of reviewer in patch 3/3.

v3:
Rebase onto v4.20-rc1
Collect Reviewed-by's on v2
Add a patch to MAINTAINERS for i2c-omap.c

Vignesh R (3):
  dt-bindings: i2c-omap: Add new compatible for AM654 SoCs
  i2c: busses: Kconfig: Enable I2C_OMAP for ARCH_K3
  MAINTAINERS: Add entry for i2c-omap driver

 Documentation/devicetree/bindings/i2c/i2c-omap.txt | 8 ++++++--
 MAINTAINERS                                        | 8 ++++++++
 drivers/i2c/busses/Kconfig                         | 2 +-
 3 files changed, 15 insertions(+), 3 deletions(-)

-- 
2.19.1


WARNING: multiple messages have this Message-ID (diff)
From: Vignesh R <vigneshr@ti.com>
To: Vignesh R <vigneshr@ti.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	linux-omap@vger.kernel.org, linux-i2c@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Tony Lindgren <tony@atomide.com>,
	Grygorii Strashko <grygorii.strashko@ti.com>
Subject: [PATCH v4 0/3] i2c-omap: Enable i2c-omap driver for AM654 SoCs
Date: Fri, 9 Nov 2018 16:44:09 +0530	[thread overview]
Message-ID: <20181109111412.24777-1-vigneshr@ti.com> (raw)

Couple of patches to enable i2c-omap driver to be used with TI's new
AM654 platforms.

v4:
Add maintainer tag instead of reviewer in patch 3/3.

v3:
Rebase onto v4.20-rc1
Collect Reviewed-by's on v2
Add a patch to MAINTAINERS for i2c-omap.c

Vignesh R (3):
  dt-bindings: i2c-omap: Add new compatible for AM654 SoCs
  i2c: busses: Kconfig: Enable I2C_OMAP for ARCH_K3
  MAINTAINERS: Add entry for i2c-omap driver

 Documentation/devicetree/bindings/i2c/i2c-omap.txt | 8 ++++++--
 MAINTAINERS                                        | 8 ++++++++
 drivers/i2c/busses/Kconfig                         | 2 +-
 3 files changed, 15 insertions(+), 3 deletions(-)

-- 
2.19.1

             reply	other threads:[~2018-11-09 11:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-09 11:14 Vignesh R [this message]
2018-11-09 11:14 ` [PATCH v4 0/3] i2c-omap: Enable i2c-omap driver for AM654 SoCs Vignesh R
2018-11-09 11:14 ` [PATCH v4 1/3] dt-bindings: i2c-omap: Add new compatible " Vignesh R
2018-11-09 11:14   ` Vignesh R
2018-11-09 11:14 ` [PATCH v4 2/3] i2c: busses: Kconfig: Enable I2C_OMAP for ARCH_K3 Vignesh R
2018-11-09 11:14   ` Vignesh R
2018-11-09 11:14 ` [PATCH v4 3/3] MAINTAINERS: Add entry for i2c-omap driver Vignesh R
2018-11-09 11:14   ` Vignesh R
2018-11-09 15:58 ` [PATCH v4 0/3] i2c-omap: Enable i2c-omap driver for AM654 SoCs 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=20181109111412.24777-1-vigneshr@ti.com \
    --to=vigneshr@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=grygorii.strashko@ti.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=tony@atomide.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.