All of lore.kernel.org
 help / color / mirror / 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
Subject: [GIT PULL] RTC fixes for 4.20
Date: Mon, 12 Nov 2018 23:04:54 +0100	[thread overview]
Message-ID: <20181112220454.GA6189@piout.net> (raw)

Linus,

Here are three fixes worth taking for 4.20.

The following changes since commit 651022382c7f8da46cb4872a545ee1da6d097d2a:

  Linux 4.20-rc1 (2018-11-04 15:37:52 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git tags/rtc-4.20-2

for you to fetch changes up to 9bde0afb7a906f1dabdba37162551565740b862d:

  rtc: pcf2127: fix a kmemleak caused in pcf2127_i2c_gather_write (2018-11-07 17:13:56 +0100)

----------------------------------------------------------------
RTC fixes for 4.20

Drivers:
 - cmos: stop exporting alarms when not supported
 - hctosys: correctly report range error
 - pcf2127: fix a memory leak

----------------------------------------------------------------
Hans de Goede (1):
      rtc: cmos: Do not export alarm rtc_ops when we do not support alarms

Maciej W. Rozycki (1):
      rtc: hctosys: Add missing range error reporting

Xulin Sun (1):
      rtc: pcf2127: fix a kmemleak caused in pcf2127_i2c_gather_write

 drivers/rtc/hctosys.c     |  4 +++-
 drivers/rtc/rtc-cmos.c    | 16 ++++++++++++----
 drivers/rtc/rtc-pcf2127.c |  3 +++
 3 files changed, 18 insertions(+), 5 deletions(-)

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

             reply	other threads:[~2018-11-12 22:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-12 22:04 Alexandre Belloni [this message]
2018-11-14 20:00 ` [GIT PULL] RTC fixes for 4.20 pr-tracker-bot

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=20181112220454.GA6189@piout.net \
    --to=alexandre.belloni@bootlin.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --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
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.