From: Aneesh V <aneesh@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] omap4: update maintainer for omap4 boards
Date: Fri, 23 Sep 2011 16:25:22 +0530 [thread overview]
Message-ID: <4E7C659A.7060305@ti.com> (raw)
In-Reply-To: <CAOSpxdbqTRpT48NmX7dGAbEXor42ajh_dq_iBcc4xDaQeNtfqA@mail.gmail.com>
Hi Steve,
On Thursday 22 September 2011 08:36 PM, Steve Sakoman wrote:
> On Thu, Sep 22, 2011 at 7:13 AM, Aneesh V<aneesh@ti.com> wrote:
>> Steve wants to transfer maintainership of OMAP4 boards
>> to me as he is not working on these boards lately.
>>
>> CC: Steve Sakoman<steve@sakoman.com>
>> CC: Sandeep Paulraj<s-paulraj@ti.com>
>> CC: Albert Aribaud<albert.u.boot@aribaud.net>
>> CC: Wolfgang Denk<wd@denx.de>
>> Signed-off-by: Aneesh V<aneesh@ti.com>
>> ---
>> MAINTAINERS | 3 +++
>> 1 files changed, 3 insertions(+), 0 deletions(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 2f60a60..bee8699 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -798,6 +798,9 @@ Nomadik Linux Team<STN_WMM_nomadik_linux@list.st.com>
>> Steve Sakoman<sakoman@gmail.com>
>>
>> omap3_overo ARM ARMV7 (OMAP3xx SoC)
>> +
>> +Aneesh V<aneesh@ti.com>
>> +
>> omap4_panda ARM ARMV7 (OMAP4xx SoC)
>> omap4_sdp4430 ARM ARMV7 (OMAP4xx SoC)
>
> Of course you have my ack for this, but I suspect that Wolfgang will
> want you to modify the patch to preserve alphabetical ordering of
> names.
I wanted to do this but didn't find any ordering in the way the names
were put. On a second look now, I realize that it is based on the last
name. I will make a V2 to correct this.
br,
Aneesh
next prev parent reply other threads:[~2011-09-23 10:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 14:13 [U-Boot] [PATCH] omap4: update maintainer for omap4 boards Aneesh V
2011-09-22 15:06 ` Steve Sakoman
2011-09-23 10:55 ` Aneesh V [this message]
2011-09-23 11:06 ` [U-Boot] [PATCH v2] " Aneesh V
2011-09-23 17:15 ` Paulraj, Sandeep
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=4E7C659A.7060305@ti.com \
--to=aneesh@ti.com \
--cc=u-boot@lists.denx.de \
/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.