public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
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.9-stable] reset: make optional functions really optional
Date: Mon, 3 Dec 2018 18:45:41 +0100	[thread overview]
Message-ID: <20181203174541.GA11260@kroah.com> (raw)
In-Reply-To: <20181203173029.18549-1-dinguyen@kernel.org>

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.
> ---
>  drivers/reset/core.c  | 48 +++++++++++++++++++++++++++++++++----------
>  include/linux/reset.h | 45 +++++++++++++++++++++++-----------------
>  2 files changed, 63 insertions(+), 30 deletions(-)

What problem is this solving?  Why is this suddenly needed now?

thanks,

greg k-h

  parent reply	other threads:[~2018-12-03 17:45 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
2018-12-03 18:43     ` Sasha Levin
2018-12-03 17:45 ` Greg KH [this message]
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=20181203174541.GA11260@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox