From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH 7/7] MAINTAINERS: add TI Keystone ARM platform
Date: Wed, 07 Aug 2013 10:49:50 -0700 [thread overview]
Message-ID: <87li4dfl1d.fsf@linaro.org> (raw)
In-Reply-To: <1375726274-26000-8-git-send-email-santosh.shilimkar@ti.com> (Santosh Shilimkar's message of "Mon, 5 Aug 2013 14:11:14 -0400")
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.
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.
Kevin
next prev parent reply other threads:[~2013-08-07 17:49 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 [this message]
2013-08-07 18:50 ` Santosh Shilimkar
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=87li4dfl1d.fsf@linaro.org \
--to=khilman@linaro.org \
--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 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).