From: Wolfram Sang <wsa@the-dreams.de>
To: Vignesh R <vigneshr@ti.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Wolfram Sang <wsa+renesas@sang-engineering.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 0/2] i2c-omap: Enable i2c-omap driver for AM654 SoCs
Date: Sun, 28 Oct 2018 22:34:50 +0000 [thread overview]
Message-ID: <20181028223450.GK1882@kunai> (raw)
In-Reply-To: <09a6b1d4-f8f4-ea90-f361-bd3a92088430@ti.com>
[-- Attachment #1: Type: text/plain, Size: 729 bytes --]
On Sat, Oct 20, 2018 at 01:23:40PM +0530, Vignesh R wrote:
>
>
> On 28-Sep-18 10:55 AM, Vignesh R wrote:
> > Couple of patches to enable i2c-omap driver to be used with TI's new
> > AM654 platforms.
> >
> >
> > Vignesh R (2):
> > dt-bindings: i2c-omap: Add new compatible for AM654 SoCs
> > i2c: busses: Kconfig: Enable I2C_OMAP for ARCH_K3
> >
> > Documentation/devicetree/bindings/i2c/i2c-omap.txt | 8 ++++++--
> > drivers/i2c/busses/Kconfig | 2 +-
> > 2 files changed, 7 insertions(+), 3 deletions(-)
> >
>
> Gentle ping...
Maintainer tags are missing. Tony is listed for this driver on OMAP2+.
Is this his realm? Do we need a specific maintainer for this driver?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-10-28 22:34 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
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 [this message]
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=20181028223450.GK1882@kunai \
--to=wsa@the-dreams.de \
--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=robh+dt@kernel.org \
--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).