From: Christoph Fritz <chf.fritz@googlemail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Troy Kisky <troy.kisky@boundarydevices.com>,
linux-rtc@vger.kernel.org, stable@vger.kernel.org,
Stefan Riedmueller <s.riedmueller@phytec.de>,
Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>
Subject: Re: rtc: m41t80rtc: recent v4.15 changes ready for stable branch 4.14
Date: Fri, 22 Dec 2017 15:47:03 +0100 [thread overview]
Message-ID: <1513954023.1940.16.camel@googlemail.com> (raw)
In-Reply-To: <20171222130533.GE18255@piout.net>
Hi Greg
On Fri, 2017-12-22 at 14:05 +0100, Alexandre Belloni wrote:
> On 22/12/2017 at 13:50:27 +0100, Christoph Fritz wrote:
> > Hey Troy and Alexandre,
> >
> > any objections asking Greg to add following recent v4.15 changes into
> > stable branch 4.14?
> >
>
> No objection, they can be safely backported.
@Greg: Could you queue the following commits for 4.14.9 ?
> > 05a03bf rtc: m41t80: remove unneeded checks from m41t80_sqw_set_rate
> > 13bb1d7 rtc: m41t80: avoid i2c read in m41t80_sqw_is_prepared
> > 2cb90ed rtc: m41t80: avoid i2c read in m41t80_sqw_recalc_rate
> > c8384bb rtc: m41t80: fix m41t80_sqw_round_rate return value
> > de6042d rtc: m41t80: m41t80_sqw_set_rate should return 0 on success
> >
> > Without these patches, deadlock warnings showing up in 4.14:
> >
> > ======================================================
> > WARNING: possible circular locking dependency detected
> > 4.14.8-00011-gd203938 #11 Not tainted
> > ------------------------------------------------------
<snip>
Thanks
-- Christoph
next prev parent reply other threads:[~2017-12-22 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 12:50 rtc: m41t80rtc: recent v4.15 changes ready for stable branch 4.14 ? Christoph Fritz
2017-12-22 13:05 ` Alexandre Belloni
2017-12-22 14:47 ` Christoph Fritz [this message]
2018-01-04 11:07 ` rtc: m41t80rtc: recent v4.15 changes ready for stable branch 4.14 Greg Kroah-Hartman
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=1513954023.1940.16.camel@googlemail.com \
--to=chf.fritz@googlemail.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-rtc@vger.kernel.org \
--cc=s.riedmueller@phytec.de \
--cc=stable@vger.kernel.org \
--cc=troy.kisky@boundarydevices.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;
as well as URLs for NNTP newsgroup(s).