From: Greg KH <gregkh@linuxfoundation.org>
To: Dinh Nguyen <dinguyen@kernel.org>
Cc: stable@vger.kernel.org, sashal@kernel.org,
Ramiro Oliveira <Ramiro.Oliveira@synopsys.com>,
Philipp Zabel <p.zabel@pengutronix.de>
Subject: Re: [PATCH for v4.19-stable 1/6] reset: make optional functions really optional
Date: Tue, 4 Dec 2018 08:26:40 +0100 [thread overview]
Message-ID: <20181204072640.GA25998@kroah.com> (raw)
In-Reply-To: <20181203214214.28612-1-dinguyen@kernel.org>
On Mon, Dec 03, 2018 at 03:42:09PM -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.
Why is this patch series needed in 4.9? You haven't provided any
justification here :(
thanks,
greg k-h
prev parent reply other threads:[~2018-12-04 7:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 21:42 [PATCH for v4.19-stable 1/6] reset: make optional functions really optional Dinh Nguyen
2018-12-03 21:42 ` [PATCH for v4.19-stable 2/6] reset: core: fix reset_control_put Dinh Nguyen
2018-12-03 21:42 ` [PATCH for v4.19-stable 3/6] reset: fix optional reset_control_get stubs to return NULL Dinh Nguyen
2018-12-03 21:42 ` [PATCH for v4.19-stable 4/6] reset: add exported __reset_control_get, return NULL if optional Dinh Nguyen
2018-12-03 21:42 ` [PATCH for v4.19-stable 5/6] reset: make device_reset_optional() really optional Dinh Nguyen
2018-12-03 21:42 ` [PATCH for v4.19-stable 6/6] reset: remove remaining WARN_ON() in <linux/reset.h> Dinh Nguyen
2018-12-04 7:26 ` Greg KH [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=20181204072640.GA25998@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Ramiro.Oliveira@synopsys.com \
--cc=dinguyen@kernel.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 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.