From: lethal@linux-sh.org (Paul Mundt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Update ARM/SHMOBILE section of MAINTAINERS
Date: Tue, 27 Nov 2012 13:23:24 +0900 [thread overview]
Message-ID: <20121127042324.GC30445@linux-sh.org> (raw)
In-Reply-To: <1353984346-25463-1-git-send-email-horms@verge.net.au>
On Tue, Nov 27, 2012 at 11:45:46AM +0900, Simon Horman wrote:
> From: Simon Horman <horms+renesas@verge.net.au>
>
> I have been handling maintenance of shmobile
> for a little over a release-cycle now and it seems
> to appropriate to update the MAINTAINERS file accordingly.
>
> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
Acked-by: Paul Mundt <lethal@linux-sh.org>
next prev parent reply other threads:[~2012-11-27 4:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 2:45 [PATCH] Update ARM/SHMOBILE section of MAINTAINERS Simon Horman
2012-11-27 4:23 ` Paul Mundt [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-11-29 0:00 [GIT PULL v2] Renesas ARM-based SoC maintainers for v3.8 #1 Simon Horman
2012-11-29 0:00 ` [PATCH] Update ARM/SHMOBILE section of MAINTAINERS Simon Horman
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=20121127042324.GC30445@linux-sh.org \
--to=lethal@linux-sh.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).