From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC][PATCH] Consolidate Samsung MAINTAINERS
Date: Thu, 01 Dec 2011 16:29:33 +0900 [thread overview]
Message-ID: <045c01ccaffa$f8976d20$e9c64760$%kim@samsung.com> (raw)
In-Reply-To: <201111291006.49821.heiko@sntech.de>
Heiko St?bner wrote:
>
> Am Dienstag, 15. November 2011, 08:11:05 schrieb Kukjin Kim:
> > Kukjin Kim wrote:
> > > Heiko St?bner wrote:
> > > > Am Sonntag 23 Oktober 2011, 00:12:14 schrieb Heiko St?bner:
> > > > > These days most Samsung stuff gets in the kernel through Kukjin
> Kim.
> > > > > This patch changes MAINTAINERS to reflect this.
> > > > >
> > > > > By adding Kukjin Kim to the maintainers for S3C2410, S3C244x and
> > > > > S3C64xx alongside Ben Dooks the extra entries become identical to
> the
> > > > > base ARM/SAMSUNG entry and can move into it.
> > > > >
> > > > > Also the S3C2416 gets a maintainer through the s3c24* wildcard -
> as
> > > > > it did not have one until now.
> > > > >
> > > > > Signed-off-by: Heiko Stuebner <heiko@sntech.de>
> > > > > ---
> > > >
> > > > ping?
> > >
> > > Hi Heiko,
> > >
> > > Basically I'm ok on this but need to get the agreement from Ben Dooks.
> >
> > Hi Ben,
> >
> > How do you think about this?
> > If you don't want this, please let me know.
> seems ok then :-)
>
Hi Heiko,
OK, will apply.
Thanks.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
prev parent reply other threads:[~2011-12-01 7:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-22 22:12 [RFC][PATCH] Consolidate Samsung MAINTAINERS Heiko Stübner
2011-11-04 11:50 ` Heiko Stübner
2011-11-05 1:21 ` Kukjin Kim
2011-11-15 7:11 ` Kukjin Kim
2011-11-29 9:06 ` Heiko Stübner
2011-12-01 7:29 ` Kukjin Kim [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='045c01ccaffa$f8976d20$e9c64760$%kim@samsung.com' \
--to=kgene.kim@samsung.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 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).