All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joonyoung Shim <jy0922.shim@samsung.com>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
	rtc-linux@googlegroups.com
Cc: linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
	a.zummo@towertech.it, alexandre.belloni@free-electrons.com,
	cw00.choi@samsung.com
Subject: [rtc-linux] Re: [PATCH 4/4] rtc: s3c: enable/disable clocks for alarm
Date: Wed, 12 Aug 2015 10:09:13 +0900	[thread overview]
Message-ID: <55CA9CB9.1050007@samsung.com> (raw)
In-Reply-To: <55CA9330.9070700@samsung.com>

On 08/12/2015 09:28 AM, Krzysztof Kozlowski wrote:
> On 11.08.2015 20:28, Joonyoung Shim wrote:
>> The clock enable/disable codes for alarm have removed from
> 
> What do you mean in this paragraph? The clock code was removing something?
> 
>> 'commit 24e1455493da ("drivers/rtc/rtc-s3c.c: delete duplicate clock
> 
> Remove the 'apostrophe.
> 
>> control")' and the clocks keep disabling even if alarm is set, so alarm
>> interrupt can't happen.
> ...and the clocks are disabled even...
> 
> 
>>
>> The s3c_rtc_setaie function can be called several times with that
>> enabled argument has same value,
> ...several times with 'enabled' argument having same value
> 
>> so it needs to check whether clocks is
>> enabled or not.
> s/is/are/
> 
>>
>> Signed-off-by: Joonyoung Shim <jy0922.shim@samsung.com>
> 
> Please add Cc-stable and fixes tag. To backport the patch probably
> you'll have to remove the dependency on previous patches.

Thanks for the point, i didn't think it.

-- 
-- 
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
--- 
You received this message because you are subscribed to the Google Groups "rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

WARNING: multiple messages have this Message-ID (diff)
From: Joonyoung Shim <jy0922.shim@samsung.com>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
	rtc-linux@googlegroups.com
Cc: linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
	a.zummo@towertech.it, alexandre.belloni@free-electrons.com,
	cw00.choi@samsung.com
Subject: Re: [PATCH 4/4] rtc: s3c: enable/disable clocks for alarm
Date: Wed, 12 Aug 2015 10:09:13 +0900	[thread overview]
Message-ID: <55CA9CB9.1050007@samsung.com> (raw)
In-Reply-To: <55CA9330.9070700@samsung.com>

On 08/12/2015 09:28 AM, Krzysztof Kozlowski wrote:
> On 11.08.2015 20:28, Joonyoung Shim wrote:
>> The clock enable/disable codes for alarm have removed from
> 
> What do you mean in this paragraph? The clock code was removing something?
> 
>> 'commit 24e1455493da ("drivers/rtc/rtc-s3c.c: delete duplicate clock
> 
> Remove the 'apostrophe.
> 
>> control")' and the clocks keep disabling even if alarm is set, so alarm
>> interrupt can't happen.
> ...and the clocks are disabled even...
> 
> 
>>
>> The s3c_rtc_setaie function can be called several times with that
>> enabled argument has same value,
> ...several times with 'enabled' argument having same value
> 
>> so it needs to check whether clocks is
>> enabled or not.
> s/is/are/
> 
>>
>> Signed-off-by: Joonyoung Shim <jy0922.shim@samsung.com>
> 
> Please add Cc-stable and fixes tag. To backport the patch probably
> you'll have to remove the dependency on previous patches.

Thanks for the point, i didn't think it.

  reply	other threads:[~2015-08-12  1:09 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-11 11:28 [rtc-linux] [PATCH 1/4] rtc: s3c: add missing clk control Joonyoung Shim
2015-08-11 11:28 ` Joonyoung Shim
2015-08-11 11:28 ` [rtc-linux] [PATCH 2/4] rtc: s3c: remove unnecessary NULL assignment Joonyoung Shim
2015-08-11 11:28   ` Joonyoung Shim
2015-08-12  0:07   ` [rtc-linux] " Krzysztof Kozlowski
2015-08-12  0:07     ` Krzysztof Kozlowski
2015-08-20 23:07   ` [rtc-linux] " Alexandre Belloni
2015-08-20 23:07     ` Alexandre Belloni
2015-08-11 11:28 ` [rtc-linux] [PATCH 3/4] rtc: s3c: use unified functions for enable/disable of clk Joonyoung Shim
2015-08-11 11:28   ` Joonyoung Shim
2015-08-12  0:10   ` [rtc-linux] " Krzysztof Kozlowski
2015-08-12  0:10     ` Krzysztof Kozlowski
2015-08-12 10:26     ` [rtc-linux] " Joonyoung Shim
2015-08-12 10:26       ` Joonyoung Shim
2015-08-11 11:28 ` [rtc-linux] [PATCH 4/4] rtc: s3c: enable/disable clocks for alarm Joonyoung Shim
2015-08-11 11:28   ` Joonyoung Shim
2015-08-12  0:28   ` [rtc-linux] " Krzysztof Kozlowski
2015-08-12  0:28     ` Krzysztof Kozlowski
2015-08-12  1:09     ` Joonyoung Shim [this message]
2015-08-12  1:09       ` Joonyoung Shim
2015-08-12  0:06 ` [rtc-linux] Re: [PATCH 1/4] rtc: s3c: add missing clk control Krzysztof Kozlowski
2015-08-12  0:06   ` Krzysztof Kozlowski
2015-08-20 23:06 ` [rtc-linux] " Alexandre Belloni
2015-08-20 23:06   ` Alexandre Belloni

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=55CA9CB9.1050007@samsung.com \
    --to=jy0922.shim@samsung.com \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=cw00.choi@samsung.com \
    --cc=k.kozlowski@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=rtc-linux@googlegroups.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.