From: nm@ti.com (Nishanth Menon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MAINTAINERS: Add keystone device tree and defconfig to list
Date: Tue, 22 Sep 2015 11:01:09 -0500 [thread overview]
Message-ID: <56017B45.9050304@ti.com> (raw)
In-Reply-To: <5601790C.9080703@oracle.com>
On 09/22/2015 10:51 AM, santosh.shilimkar at oracle.com wrote:
> On 9/22/15 8:39 AM, Nishanth Menon wrote:
>> Keystone2 architecture files also include defconfig and devicetree
>> files which need maintainer to pick up and send for merge. Include the
>> same in the MAINTAINERS file so that we know where what needs to go.
>>
> Well this is I guess assumed responsibility and I have been taking
> care of those patches.
Yes, indeed.. Thanks for doing the same :)
>
>> Cc: Santosh Shilimkar <ssantosh@kernel.org>
>> Cc: linux-arm-kernel at lists.infradead.org
>> Signed-off-by: Nishanth Menon <nm@ti.com>
>> ---
>> MAINTAINERS | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 7ba7ab749c85..5a06d3e26c80 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -1187,6 +1187,9 @@ ARM/TEXAS INSTRUMENT KEYSTONE ARCHITECTURE
>> M: Santosh Shilimkar <ssantosh@kernel.org>
>> L: linux-arm-kernel at lists.infradead.org (moderated for
>> non-subscribers)
>> S: Maintained
>> +F: arch/arm/boot/dts/k2*
>> +F: arch/arm/boot/dts/keystone*
>> +F: arch/arm/configs/keystone_defconfig
>> F: arch/arm/mach-keystone/
>> T: git
>> git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux-keystone.git
>>
> No harm in adding explicitly if it helps. :-)
>
> Acked-by: Santosh Shilimkar <ssantosh@kernel.org>
>
Thanks.
--
Regards,
Nishanth Menon
WARNING: multiple messages have this Message-ID (diff)
From: Nishanth Menon <nm@ti.com>
To: "santosh.shilimkar@oracle.com" <santosh.shilimkar@oracle.com>,
Nishanth Menon <nm@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] MAINTAINERS: Add keystone device tree and defconfig to list
Date: Tue, 22 Sep 2015 11:01:09 -0500 [thread overview]
Message-ID: <56017B45.9050304@ti.com> (raw)
In-Reply-To: <5601790C.9080703@oracle.com>
On 09/22/2015 10:51 AM, santosh.shilimkar@oracle.com wrote:
> On 9/22/15 8:39 AM, Nishanth Menon wrote:
>> Keystone2 architecture files also include defconfig and devicetree
>> files which need maintainer to pick up and send for merge. Include the
>> same in the MAINTAINERS file so that we know where what needs to go.
>>
> Well this is I guess assumed responsibility and I have been taking
> care of those patches.
Yes, indeed.. Thanks for doing the same :)
>
>> Cc: Santosh Shilimkar <ssantosh@kernel.org>
>> Cc: linux-arm-kernel@lists.infradead.org
>> Signed-off-by: Nishanth Menon <nm@ti.com>
>> ---
>> MAINTAINERS | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 7ba7ab749c85..5a06d3e26c80 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -1187,6 +1187,9 @@ ARM/TEXAS INSTRUMENT KEYSTONE ARCHITECTURE
>> M: Santosh Shilimkar <ssantosh@kernel.org>
>> L: linux-arm-kernel@lists.infradead.org (moderated for
>> non-subscribers)
>> S: Maintained
>> +F: arch/arm/boot/dts/k2*
>> +F: arch/arm/boot/dts/keystone*
>> +F: arch/arm/configs/keystone_defconfig
>> F: arch/arm/mach-keystone/
>> T: git
>> git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux-keystone.git
>>
> No harm in adding explicitly if it helps. :-)
>
> Acked-by: Santosh Shilimkar <ssantosh@kernel.org>
>
Thanks.
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2015-09-22 16:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 15:39 [PATCH] MAINTAINERS: Add keystone device tree and defconfig to list Nishanth Menon
2015-09-22 15:39 ` Nishanth Menon
2015-09-22 15:51 ` santosh.shilimkar at oracle.com
2015-09-22 15:51 ` santosh.shilimkar
2015-09-22 16:01 ` Nishanth Menon [this message]
2015-09-22 16:01 ` Nishanth Menon
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=56017B45.9050304@ti.com \
--to=nm@ti.com \
--cc=linux-arm-kernel@lists.infradead.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 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.