From: Tony Lindgren <tony@atomide.com>
To: Vignesh R <vigneshr@ti.com>
Cc: Wolfram Sang <wsa@the-dreams.de>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Rob Herring <robh+dt@kernel.org>,
"Strashko, Grygorii" <grygorii.strashko@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 3/3] MAINTAINERS: Add entry for i2c-omap driver
Date: Thu, 8 Nov 2018 07:02:31 -0800 [thread overview]
Message-ID: <20181108150231.GF56134@atomide.com> (raw)
In-Reply-To: <d57ace5e-d42a-0a0e-2813-4a25cc6b37bb@ti.com>
* Vignesh R <vigneshr@ti.com> [181108 12:28]:
>
>
> On 08/11/18 2:53 PM, Wolfram Sang wrote:
> > On Thu, Nov 08, 2018 at 02:49:31PM +0530, Vignesh R wrote:
> >> Add separate entry for i2c-omap and add my name as reviewer for this
> >> driver.
> >
> > Thanks for stepping up, yet out of curiosity: why not maintainer?
> >
>
> I wasn't sure whether the convention is to add Reviewer or Maintainer
> entry for individual driver. I would be glad to change entry to maintainer.
Great, yes please do!
Regards,
Tony
next prev parent reply other threads:[~2018-11-08 15:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 9:19 [PATCH v3 0/3] i2c-omap: Enable i2c-omap driver for AM654 SoCs Vignesh R
2018-11-08 9:19 ` Vignesh R
2018-11-08 9:19 ` [PATCH v3 1/3] dt-bindings: i2c-omap: Add new compatible " Vignesh R
2018-11-08 9:19 ` Vignesh R
2018-11-08 9:19 ` [PATCH v3 2/3] i2c: busses: Kconfig: Enable I2C_OMAP for ARCH_K3 Vignesh R
2018-11-08 9:19 ` Vignesh R
2018-11-08 9:19 ` [PATCH v3 3/3] MAINTAINERS: Add entry for i2c-omap driver Vignesh R
2018-11-08 9:19 ` Vignesh R
2018-11-08 9:23 ` Wolfram Sang
2018-11-08 12:28 ` Vignesh R
2018-11-08 15:02 ` Tony Lindgren [this message]
2018-11-09 15:55 ` Wolfram Sang
2018-11-09 15:56 ` Wolfram Sang
2018-11-09 16:10 ` Tony Lindgren
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=20181108150231.GF56134@atomide.com \
--to=tony@atomide.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=vigneshr@ti.com \
--cc=wsa+renesas@sang-engineering.com \
--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 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.