Linux-RTC Archive on lore.kernel.org
 help / color / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-rtc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Olof Johansson <olof@lixom.net>
Subject: Re: [GIT PULL] RTC for 5.2
Date: Fri, 10 May 2019 16:38:16 +0200
Message-ID: <20190510143816.GB7622@piout.net> (raw)
In-Reply-To: <20190509210340.GA23061@piout.net>

On 09/05/2019 23:03:40+0200, Alexandre Belloni wrote:
> Hello Linus,
> 
> A huge series from me this cycle. I went through many drivers to set the
> date and time range supported by the RTC which helps solving HW
> limitation when the time comes (as early as next year for some). This
> time, I focused on drivers using .set_mms and .set_mmss64, allowing me
> to remove those callbacks. About a third of the patches got reviews, I
> actually own the RTCs and I tested another third and the remaining one
> are unlikely to cause any issues.
> 
> Other than that, a single new driver and the usual fixes here and there.
> 
> The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
> 
>   Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git tags/rtc-5.2
> 
> for you to fetch changes up to dacb6a4035a010e41abaf81c1cfe2beadfb05ec8:
> 
>   rtc: snvs: Use __maybe_unused instead of #if CONFIG_PM_SLEEP (2019-05-08 22:14:36 +0200)
> 

I forgot to mention that you will have a non trivial conflict that is
properly resolved in linux-next when you will pull arm-soc.

There is no need to check the return value of tm2bcd() after
35118b7a4ea0 ("rtc: omap: let the core handle range")


-- 
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      parent reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-09 21:03 Alexandre Belloni
2019-05-09 22:15 ` pr-tracker-bot
2019-05-10 14:38 ` Alexandre Belloni [this message]

Reply instructions:

You may reply publically 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=20190510143816.GB7622@piout.net \
    --to=alexandre.belloni@bootlin.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=torvalds@linux-foundation.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

Linux-RTC Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-rtc/0 linux-rtc/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-rtc linux-rtc/ https://lore.kernel.org/linux-rtc \
		linux-rtc@vger.kernel.org linux-rtc@archiver.kernel.org
	public-inbox-index linux-rtc


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-rtc


AGPL code for this site: git clone https://public-inbox.org/ public-inbox