Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Markus Reichl <m.reichl@fivetechno.de>
To: Javier Martinez Canillas <javier.martinez@collabora.co.uk>,
	linux-samsung-soc@vger.kernel.org
Cc: Anand Moon <linux.amoon@gmail.com>,
	Krzysztof Kozlowski <k.kozlowski@samsung.com>,
	cw00.choi@samsung.com
Subject: Re: [PATCH V4 2/2] ARM: dts: exynos5422-odroidxu3: add 'rtc_src' clock to rtc node
Date: Tue, 31 Mar 2015 14:06:51 +0200	[thread overview]
Message-ID: <551A8DDB.9060307@fivetechno.de> (raw)
In-Reply-To: <551A8C4E.2030400@collabora.co.uk>

[-- Attachment #1: Type: text/plain, Size: 953 bytes --]

Am 31.03.2015 um 14:00 schrieb Javier Martinez Canillas:
> Hello Markus,
> 
> On 03/31/2015 01:48 PM, Markus Reichl wrote:
>> The Exynos5422 SoC has a s3c6410 RTC where the source clock
>> is now a mandatory property.
>>
>> This patch fixes probe failure of s3c-rtc on Odroid-XU3 boards.
>> It is based on v4.0-rc2.
>>
>> ---
>> Changes since v3:
>> 1. Readded slipped #include statement.
>> Sorry for the mess.
>> Changes since v2:
>> 1. Dropped unused phandle.
>> Changes since v1:
>> 1. Dropped Documentation.
>> 2. Split into 2 parts.
>>
>> Signed-off-by: Markus Reichl <m.reichl@fivetechno.de>
>>
> 
> When you re-spin your patches with small changes, you should keep all
> the {Reviewed,Tested,Acked}-by tags collected on previous versions so
> the maintainer picking the patches knows who already reviewed the code.
> 
> Best regards,
> Javier
> 
> 
Ok, will copy it in next time.

Thanks,
-- 
Markus Reichl


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2015-03-31 12:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-31 11:48 [PATCH V4 2/2] ARM: dts: exynos5422-odroidxu3: add 'rtc_src' clock to rtc node Markus Reichl
2015-03-31 12:00 ` Javier Martinez Canillas
2015-03-31 12:06   ` Markus Reichl [this message]
2015-05-02  5:14 ` Krzysztof Kozlowski
2015-05-03 16:34   ` [RESEND] " Markus Reichl

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=551A8DDB.9060307@fivetechno.de \
    --to=m.reichl@fivetechno.de \
    --cc=cw00.choi@samsung.com \
    --cc=javier.martinez@collabora.co.uk \
    --cc=k.kozlowski@samsung.com \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux.amoon@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox