From: Balaji T K <balajitk@ti.com>
To: Venkatraman S <svenkatr@gmail.com>
Cc: linux-mmc@vger.kernel.org, cjb@laptop.org,
linux-omap@vger.kernel.org, balbi@ti.com
Subject: Re: [PATCH] mmc: omap_hsmmc: MAINTAINERS: update
Date: Mon, 4 Feb 2013 20:37:14 +0530 [thread overview]
Message-ID: <510FCEA2.8010507@ti.com> (raw)
In-Reply-To: <CAOyx1Lq=WNrpXKtd07iZJ-hTFBt-W=6GUDTqX+15ByPEhfezmw@mail.gmail.com>
On Thursday 31 January 2013 02:52 PM, Venkatraman S wrote:
> On Thu, Jan 31, 2013 at 2:22 PM, Balaji T K <balajitk@ti.com> wrote:
>> Update Maintainer email for omap_hsmmc,
>> as Venkatraman will no longer be able to maintain omap_hsmmc driver.
>>
>> Signed-off-by: Venkatraman S <svenkatr@gmail.com>
>> Signed-off-by: Balaji T K <balajitk@ti.com>
>
> Balaji,
> My sign-off is incorrect, as I did not write this patch.
>
> Of course it would great to have a maintainer for this, hence you can add my
> Acked-by: Venkatraman S <svenkatr@gmail.com>
Thanks for acking Venkat :-)
yes, you didn't write this patch entirely,
I retained your sign-off because I just modified your
patch[1] to add myself as maintainer :-)
[1]
http://comments.gmane.org/gmane.linux.kernel.mmc/18703
Anyways let me know If you would still like to have your sign-off
dropped from this patch.
>
>> ---
>> MAINTAINERS | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
next prev parent reply other threads:[~2013-02-04 15:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 13:30 [PATCH] mmc: omap_hsmmc: MAINTAINERS: change omap_hsmmc maintenance to orphan Venkatraman S
2013-01-28 21:33 ` Chris Ball
2013-01-30 16:52 ` Balaji T K
2013-01-30 16:57 ` Chris Ball
2013-01-31 8:52 ` [PATCH] mmc: omap_hsmmc: MAINTAINERS: update Balaji T K
2013-01-31 9:22 ` Venkatraman S
2013-02-04 15:07 ` Balaji T K [this message]
2013-02-06 14:34 ` [PATCH v2] " Balaji T K
2013-02-11 16:44 ` Chris Ball
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=510FCEA2.8010507@ti.com \
--to=balajitk@ti.com \
--cc=balbi@ti.com \
--cc=cjb@laptop.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=svenkatr@gmail.com \
/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.