Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Heiko St??bner <heiko@sntech.de>,
	Kukjin Kim <kgene.kim@samsung.com>,
	linaro-dev@lists.linaro.org, patches@linaro.org,
	linux-samsung-soc@vger.kernel.org, ben-linux@fluff.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] ARM: S3C64xx: cpuidle cleanups
Date: Mon, 14 May 2012 15:44:35 +0200	[thread overview]
Message-ID: <4FB10C43.9060901@linaro.org> (raw)
In-Reply-To: <20120514085700.GA2189@sirena.org.uk>

On 05/14/2012 10:57 AM, Mark Brown wrote:
> On Mon, May 14, 2012 at 10:52:46AM +0200, Heiko St??bner wrote:
>> Am Montag, 14. Mai 2012, 01:51:00 schrieb Daniel Lezcano:
>>> On 05/09/2012 04:08 PM, Daniel Lezcano wrote:
>>> Are these patches ok for inclusion ?
>> you might want to include the maintainer
>> 	Kukjin Kim<kgene.kim@samsung.com>
>> and the samsung list
>> 	linux-samsung-soc@vger.kernel.org
>> into your recipients
> Also the original author (me).

Mark,

I noticed you are not in the cpuidle.c header file neither in the 
MAINTAINERS entry for the s3c64xx.
Just FYI.

Thanks
-- Daniel


-- 
  <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

  parent reply	other threads:[~2012-05-14 13:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1336572489-21457-1-git-send-email-daniel.lezcano@linaro.org>
     [not found] ` <4FB048E4.8070405@linaro.org>
2012-05-14  8:52   ` [PATCH 0/2] ARM: S3C64xx: cpuidle cleanups Heiko Stübner
2012-05-14  8:57     ` Mark Brown
2012-05-14  9:22       ` Daniel Lezcano
2012-05-14 13:51         ` Kukjin Kim
2012-05-14 13:56           ` Daniel Lezcano
2012-05-14 13:44       ` Daniel Lezcano [this message]
2012-05-14 14:06 Daniel Lezcano
2012-05-17  6:57 ` Kukjin Kim

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=4FB10C43.9060901@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=ben-linux@fluff.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=heiko@sntech.de \
    --cc=kgene.kim@samsung.com \
    --cc=linaro-dev@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=patches@linaro.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