From: Dinh Nguyen <dinguyen@kernel.org>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, gregkh@linuxfoundation.org,
Philipp Zabel <p.zabel@pengutronix.de>
Subject: Re: [PATCH for v4.9-stable] reset: make optional functions really optional
Date: Mon, 3 Dec 2018 12:31:59 -0600 [thread overview]
Message-ID: <7c56aa7e-f86c-e1d8-ad65-ca35c287ce75@kernel.org> (raw)
In-Reply-To: <20181203174422.GM235790@sasha-vm>
On 12/3/18 11:44 AM, Sasha Levin wrote:
> On Mon, Dec 03, 2018 at 11:30:29AM -0600, Dinh Nguyen wrote:
>> From: Ramiro Oliveira <Ramiro.Oliveira@synopsys.com>
>>
>> commit bb475230b8e59a547ab66ac3b02572df21a580e9 upstream.
>>
>> The *_get_optional_* functions weren't really optional so this patch
>> makes them really optional.
>>
>> These *_get_optional_* functions will now return NULL instead of an error
>> if no matching reset phandle is found in the DT, and all the
>> reset_control_* functions now accept NULL rstc pointers.
>>
>> Signed-off-by: Ramiro Oliveira <Ramiro.Oliveira@synopsys.com>
>> Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
>> ---
>> Please apply to v4.9.y stable tree.
>
> The original commit had a few upstream fixes:
>
> bb6c7768385b reset: remove remaining WARN_ON() in <linux/reset.h>
> 1554bbd4ad40 reset: make device_reset_optional() really optional
> 62e24c5775ec reset: add exported __reset_control_get, return NULL if
> optional
> 0ca10b60ceeb reset: fix optional reset_control_get stubs to return NULL
> 4891486fb2c8 reset: core: fix reset_control_put
>
> We'll need to backport them to 4.9 as well if you backport this commit.
>
Hmm..I was able to fix an ethernet driver load issue by just backporting
this patch. Should I investigate backport of the other patches as well?
Dinh
next prev parent reply other threads:[~2018-12-03 18:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 17:30 [PATCH for v4.9-stable] reset: make optional functions really optional Dinh Nguyen
2018-12-03 17:44 ` Sasha Levin
2018-12-03 18:31 ` Dinh Nguyen [this message]
2018-12-03 18:43 ` Sasha Levin
2018-12-03 17:45 ` Greg KH
2018-12-03 18:28 ` Dinh Nguyen
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=7c56aa7e-f86c-e1d8-ad65-ca35c287ce75@kernel.org \
--to=dinguyen@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=p.zabel@pengutronix.de \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.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