Linux RTC
 help / color / mirror / Atom feed
From: Keerthy <a0393675@ti.com>
To: Tony Lindgren <tony@atomide.com>,
	Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: Keerthy <j-keerthy@ti.com>, <bcousson@baylibre.com>,
	<johan@kernel.org>, <linux-omap@vger.kernel.org>,
	<rtc-linux@googlegroups.com>, <grygorii.strashko@ti.com>
Subject: [rtc-linux] Re: [PATCH v5 0/3] ARM: AM437X: Add rtc clock handling
Date: Tue, 1 Sep 2015 22:48:16 +0530	[thread overview]
Message-ID: <55E5DDD8.6060400@ti.com> (raw)
In-Reply-To: <20150901152740.GH4215@atomide.com>



On Tuesday 01 September 2015 08:57 PM, Tony Lindgren wrote:
> * Alexandre Belloni <alexandre.belloni@free-electrons.com> [150826 14:57]:
>> On 26/08/2015 at 11:01:27 -0700, Tony Lindgren wrote :
>>> * Keerthy <a0393675@ti.com> [150826 09:54]:
>>>> Tony,
>>>>
>>>> On Saturday 22 August 2015 02:48 AM, Alexandre Belloni wrote:
>>>>> Tony,
>>>>>
>>>>> On 18/08/2015 at 15:11:13 +0530, Keerthy wrote :
>>>>>> The series is applicable for all am437x series of processors.
>>>>>> It adds clock handling support. Boot tested on am437x-gp-evm.
>>>>>>
>>>>>> Keerthy (3):
>>>>>>    ARM: dts: AM437x: Add the internal and external clock nodes for rtc
>>>>>>    rtc: omap: Add internal clock enabling support
>>>>>>    rtc: omap: Add external clock enabling support
>>>>>>
>>>>>
>>>>> I'm wondering how you want to get those patches merged. I can let you
>>>>> take 2 and 3 through arm-soc but you will miss 4.3. Or I can take 2 and
>>>>> 3 for 4.3 but the documentation will be missing.
>>>>
>>>> A gentle ping on this series.
>>>
>>> Alexandre, it's probably best that you take them all. The dts changes
>>> apply against Linux next with fuzz so there should not be any merge
>>> conflict. Feel free to add:
>>>
>>> Acked-by: Tony Lindgren <tony@atomide.com>
>>>
>>
>> So, I've rebased 1/3 on rtc-next to avoid depending on arm-soc. I've
>> pushed everything and hopefully there won't be any issues in linux-next.
>> We are quite close to the merge window so I would be much more confident
>> sending them to Linus if you could test linux-next once the patches land
>> there.
>
> Keerthy, I presume you have now tested these with Linux next?

Yes. When i had posted v5. I tested them.

>
> Regards,
>
> Tony
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

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

      reply	other threads:[~2015-09-01 17:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-18  9:41 [rtc-linux] [PATCH v5 0/3] ARM: AM437X: Add rtc clock handling Keerthy
2015-08-18  9:41 ` [rtc-linux] [PATCH v5 1/3] ARM: dts: AM437x: Add the internal and external clock nodes for rtc Keerthy
2015-08-18  9:41 ` [rtc-linux] [PATCH v5 2/3] rtc: omap: Add internal clock enabling support Keerthy
2015-08-21 21:36   ` [rtc-linux] " Alexandre Belloni
2015-08-24  4:39     ` Keerthy
2015-08-18  9:41 ` [rtc-linux] [PATCH v5 3/3] rtc: omap: Add external " Keerthy
2015-08-21 21:18 ` [rtc-linux] Re: [PATCH v5 0/3] ARM: AM437X: Add rtc clock handling Alexandre Belloni
2015-08-26 16:51   ` Keerthy
2015-08-26 18:01     ` Tony Lindgren
2015-08-26 21:53       ` Alexandre Belloni
2015-09-01 15:27         ` Tony Lindgren
2015-09-01 17:18           ` Keerthy [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=55E5DDD8.6060400@ti.com \
    --to=a0393675@ti.com \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=bcousson@baylibre.com \
    --cc=grygorii.strashko@ti.com \
    --cc=j-keerthy@ti.com \
    --cc=johan@kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=rtc-linux@googlegroups.com \
    --cc=tony@atomide.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