From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH 7/7] MAINTAINERS: add TI Keystone ARM platform
Date: Wed, 7 Aug 2013 14:50:28 -0400 [thread overview]
Message-ID: <520296F4.7060300@ti.com> (raw)
In-Reply-To: <87li4dfl1d.fsf@linaro.org>
On Wednesday 07 August 2013 01:49 PM, Kevin Hilman wrote:
> Santosh Shilimkar <santosh.shilimkar@ti.com> writes:
>
>> Adding maintainer for arch/arm/mach-keystone/
>>
>> Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
>
> Since I'm colleting some MAINTAINERS changes, I applied this one to
> arm-soc/fixes.
>
Thanks
> The rest of the series looks good to me. Are you still waiting for any
> more feedback? If not, are you planning to send a pull request? or
> I could just apply 1-6 for fixes-non-critical.
>
I will send a pull request dropping the last patch which you already
applied.
Regards,
Santosh
prev parent reply other threads:[~2013-08-07 18:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 18:11 [RESEND PATCH 0/7] ARM: keystone: Few non-critical fixes, cleanups for 3.12 Santosh Shilimkar
2013-08-05 18:11 ` [RESEND PATCH 1/7] ARM: keystone: drop useless HAVE_SCHED_CLOCK Santosh Shilimkar
2013-08-05 18:11 ` [RESEND PATCH 2/7] ARM: keystone: remove redundant smp_init_cpus definition Santosh Shilimkar
2013-08-05 18:11 ` [RESEND PATCH 3/7] ARM: Keystone: No need to preserve r12 across smc call Santosh Shilimkar
2013-08-05 18:11 ` [RESEND PATCH 4/7] ARM: keystone: Drop the un-necessary dsb from keystone_cpu_smc() Santosh Shilimkar
2013-08-05 18:11 ` [RESEND PATCH 5/7] ARM: keystone: use #include to include skeleton.dtsi Santosh Shilimkar
2013-08-05 18:11 ` [RESEND PATCH 6/7] ARM: Keystone: Convert device tree file to use IRQ defines Santosh Shilimkar
2013-08-05 18:11 ` [RESEND PATCH 7/7] MAINTAINERS: add TI Keystone ARM platform Santosh Shilimkar
2013-08-07 17:49 ` Kevin Hilman
2013-08-07 18:50 ` Santosh Shilimkar [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=520296F4.7060300@ti.com \
--to=santosh.shilimkar@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.