linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	Kukjin Kim <kgene@kernel.org>, Kukjin Kim <kgene.kim@samsung.com>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	linux-samsung-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpuidle: add MAINTAINERS entry for ARM Exynos cpuidle driver
Date: Wed, 03 Dec 2014 10:06:36 +0100	[thread overview]
Message-ID: <547ED29C.4010006@linaro.org> (raw)
In-Reply-To: <1466322.AKaPtIKjPo@vostro.rjw.lan>

On 12/03/2014 01:08 AM, Rafael J. Wysocki wrote:
> On Tuesday, December 02, 2014 04:41:35 PM Bartlomiej Zolnierkiewicz wrote:
>> Since there has been quite a lot of development going on for
>> ARM Exynos cpuidle driver recently I would like to add separate
>> MAINTAINERS entry for it and add myself as the primary maintainer.
>>
>> The merging process would remain (almost) unchanged with patches
>> going (with my Ack) through Daniel's or Kukjin's tree.
>>
>> Signed-off-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
>> Acked-by: Kyungmin Park <kyungmin.park@samsung.com>
>
> Daniel, do you want me to apply this, or are you going to do that?

Please apply it.

Thanks !
  -- Daniel

>> ---
>>   MAINTAINERS |   10 ++++++++++
>>   1 file changed, 10 insertions(+)
>>
>> Index: b/MAINTAINERS
>> ===================================================================
>> --- a/MAINTAINERS	2014-11-27 18:02:51.988225868 +0100
>> +++ b/MAINTAINERS	2014-12-02 15:56:52.792997513 +0100
>> @@ -2701,6 +2701,16 @@ T:	git git://git.kernel.org/pub/scm/linu
>>   S:	Maintained
>>   F:	drivers/cpuidle/cpuidle-big_little.c
>>
>> +CPUIDLE DRIVER - ARM EXYNOS
>> +M:	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
>> +M:	Daniel Lezcano <daniel.lezcano@linaro.org>
>> +M:	Kukjin Kim <kgene@kernel.org>
>> +L:	linux-pm@vger.kernel.org
>> +L:	linux-samsung-soc@vger.kernel.org
>> +S:	Supported
>> +F:	drivers/cpuidle/cpuidle-exynos.c
>> +F:	arch/arm/mach-exynos/pm.c
>> +
>>   CPUIDLE DRIVERS
>>   M:	Rafael J. Wysocki <rjw@rjwysocki.net>
>>   M:	Daniel Lezcano <daniel.lezcano@linaro.org>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-pm" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


-- 
  <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

      reply	other threads:[~2014-12-03  9:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-02 15:41 [PATCH] cpuidle: add MAINTAINERS entry for ARM Exynos cpuidle driver Bartlomiej Zolnierkiewicz
2014-12-03  0:08 ` Rafael J. Wysocki
2014-12-03  9:06   ` Daniel Lezcano [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=547ED29C.4010006@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=b.zolnierkie@samsung.com \
    --cc=kgene.kim@samsung.com \
    --cc=kgene@kernel.org \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    /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).