From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Reset controller fixes for v4.11
Date: Tue, 21 Mar 2017 17:31:08 -0700 [thread overview]
Message-ID: <20170322003108.GD5129@localhost> (raw)
In-Reply-To: <1490117743.6403.8.camel@pengutronix.de>
On Tue, Mar 21, 2017 at 06:35:43PM +0100, Philipp Zabel wrote:
> Dear arm-soc maintainers,
>
> please consider merging this tag, which completes an already merged
> commit in case the RESET_CONTROLLER config option is disabled.
>
> I have already sent a few patches that make use of the new behaviour
> introduced by commit bb475230b8e5 ("reset: make optional functions
> really optional"). It would be nice if those could be merged for v4.11,
> as without this fix they could cause drivers to fail probing if
> RESET_CONTROLLER is disabled.
>
> regards
> Philipp
>
> The following changes since commit c1ae3cfa0e89fa1a7ecc4c99031f5e9ae99d9201:
>
> Linux 4.11-rc1 (2017-03-05 12:59:56 -0800)
>
> are available in the git repository at:
>
> git://git.pengutronix.de/git/pza/linux.git tags/reset-fixes-for-4.11
>
> for you to fetch changes up to 0ca10b60ceeb5372da01798ca68c116ae45a6eb6:
>
> reset: fix optional reset_control_get stubs to return NULL (2017-03-21 18:19:43 +0100)
>
> ----------------------------------------------------------------
> Reset controller fixes for v4.11
>
> Fix optional reset_control_get_stubs to return NULL and remove warnings
> from reset_control_* stubs.
> This fixes commit bb475230b8e5 ("reset: make optional functions really
> optional"), which was merged in reset-for-4.11, and would cause consumer
> drivers depending on the new behaviour of optional resets to fail probing
> if RESET_CONTROLLER Kconfig option is disabled.
Merged, thanks!
-Olof
prev parent reply other threads:[~2017-03-22 0:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 17:35 [GIT PULL] Reset controller fixes for v4.11 Philipp Zabel
2017-03-22 0:31 ` 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=20170322003108.GD5129@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).