linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kishon Vijay Abraham I <kishon@ti.com>
To: Rob Herring <robh@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	<devicetree@vger.kernel.org>,
	"Gustavo A. R. Silva" <gustavo@embeddedor.com>
Subject: Re: [PATCH] MAINTAINERS: Add Kishon as maintainer of PHY bindings
Date: Tue, 20 Nov 2018 11:09:25 +0530	[thread overview]
Message-ID: <5b1104bc-7542-124c-2f93-27af10e36178@ti.com> (raw)
In-Reply-To: <CAL_JsqJn2EOGJaM9saoYYnbZ+GrEMQWgp_1kSq6W9HX1GnGVWw@mail.gmail.com>

Hi Rob,

On 17/11/18 1:50 AM, Rob Herring wrote:
> On Thu, Oct 18, 2018 at 8:31 AM Rob Herring <robh@kernel.org> wrote:
>>
>> DT bindings normally go in via subsystem maintainers, so add PHY
>> bindings under generic PHY framework.
>>
>> Reported-by: Gustavo A. R. Silva <gustavo@embeddedor.com>
>> Cc: Kishon Vijay Abraham I <kishon@ti.com>
>> Signed-off-by: Rob Herring <robh@kernel.org>
> 
> Ping? Kishon, any objection?

It's queued [1].

Thanks
Kishon

[1] -> 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/MAINTAINERS?id=5c7412b139f189e18842d62951f6857e4937ce73
> 
>> ---
>>   MAINTAINERS | 1 +
>>   1 file changed, 1 insertion(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 9ad052aeac39..b01e77ae79c4 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -6132,6 +6132,7 @@ T:        git git://git.kernel.org/pub/scm/linux/kernel/git/kishon/linux-phy.git
>>   S:     Supported
>>   F:     drivers/phy/
>>   F:     include/linux/phy/
>> +F:     Documentation/devicetree/bindings/phy/
>>
>>   GENERIC PINCTRL I2C DEMULTIPLEXER DRIVER
>>   M:     Wolfram Sang <wsa+renesas@sang-engineering.com>
>> --
>> 2.17.1
>>

      reply	other threads:[~2018-11-20  5:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-18 13:31 [PATCH] MAINTAINERS: Add Kishon as maintainer of PHY bindings Rob Herring
2018-11-16 20:20 ` Rob Herring
2018-11-20  5:39   ` Kishon Vijay Abraham I [this message]

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=5b1104bc-7542-124c-2f93-27af10e36178@ti.com \
    --to=kishon@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gustavo@embeddedor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    /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).