From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Reset controller changes for v4.11
Date: Sun, 29 Jan 2017 14:29:39 -0800 [thread overview]
Message-ID: <20170129222939.GA3133@localhost> (raw)
In-Reply-To: <1484933170.2897.76.camel@pengutronix.de>
On Fri, Jan 20, 2017 at 06:26:10PM +0100, Philipp Zabel wrote:
> Dear arm-soc maintainers,
>
> Please consider merging this tag which adds reset controller drivers for
> Hi3660 and ZX2967 SoCs and adds SD reset support for LD11 SoCs. It makes
> the API describe optional and not present reset controls as NULL
> pointers, which will allow some drivers to simplify their return value
> handling. There also is a ti_syscon status return value fix, a typo fix,
> and some constification.
>
> regards
> Philipp
>
> The following changes since commit a121103c922847ba5010819a3f250f1f7fc84ab8:
>
> Linux 4.10-rc3 (2017-01-08 14:18:17 -0800)
>
> are available in the git repository at:
>
> git://git.pengutronix.de/pza/linux tags/reset-for-4.11
>
> for you to fetch changes up to bb475230b8e59a547ab66ac3b02572df21a580e9:
>
> reset: make optional functions really optional (2017-01-20 10:36:15 +0100)
>
> ----------------------------------------------------------------
> Reset controller changes for v4.11
>
> - fix ti_syscon reset_status reporting
> - add Hisilicon Hi3660 reset controller driver
> - add ZTE ZX2967 reset controller driver
> - add LD11 SD-reset block to uniphier reset controller driver
> - typo and correctness fixes
> - make reset_control_get variants return NULL instead of an
> error for optional, not specified resets and have the other
> reset API functions silently ignore rstc == NULL parameters.
Merged, thanks.
-Olof
prev parent reply other threads:[~2017-01-29 22:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 17:26 [GIT PULL] Reset controller changes for v4.11 Philipp Zabel
2017-01-29 22:29 ` Olof Johansson [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=20170129222939.GA3133@localhost \
--to=olof@lixom.net \
--cc=linux-arm-kernel@lists.infradead.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 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).