From: Bjorn Helgaas <helgaas@kernel.org>
To: Jim Quinlan <jim2101024@gmail.com>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: Amjad Ouled-Ameur <aouledameur@baylibre.com>,
linux-pci@vger.kernel.org,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
bcm-kernel-feedback-list@broadcom.com,
james.quinlan@broadcom.com, stable@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 1/3] reset: add missing empty function reset_control_rearm()
Date: Mon, 3 May 2021 13:56:39 -0500 [thread overview]
Message-ID: <20210503185639.GA993318@bjorn-Precision-5520> (raw)
In-Reply-To: <20210430152156.21162-2-jim2101024@gmail.com>
On Fri, Apr 30, 2021 at 11:21:54AM -0400, Jim Quinlan wrote:
> All other functions are defined for when CONFIG_RESET_CONTROLLER
> is not set.
>
> Fixes: 557acb3d2cd9 ("reset: make shared pulsed reset controls re-triggerable")
> CC: stable@vger.kernel.org # v5.11+
> Signed-off-by: Jim Quinlan <jim2101024@gmail.com>
Philipp, I'd like to merge this via the PCI tree since the brcmstb
patch depends on it. It looks correct to me, but I'd really like to
have your ack before merging it.
> ---
> include/linux/reset.h | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/include/linux/reset.h b/include/linux/reset.h
> index b9109efa2a5c..9700124affa3 100644
> --- a/include/linux/reset.h
> +++ b/include/linux/reset.h
> @@ -47,6 +47,11 @@ static inline int reset_control_reset(struct reset_control *rstc)
> return 0;
> }
>
> +static inline int reset_control_rearm(struct reset_control *rstc)
> +{
> + return 0;
> +}
> +
> static inline int reset_control_assert(struct reset_control *rstc)
> {
> return 0;
> --
> 2.17.1
>
next prev parent reply other threads:[~2021-05-03 18:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210430152156.21162-1-jim2101024@gmail.com>
2021-04-30 15:21 ` [PATCH v6 1/3] reset: add missing empty function reset_control_rearm() Jim Quinlan
2021-05-03 18:56 ` Bjorn Helgaas [this message]
2021-05-10 7:45 ` Philipp Zabel
2021-05-10 18:54 ` Bjorn Helgaas
[not found] <20210430151949.20849-1-jim2101024@gmail.com>
2021-04-30 15:19 ` Jim Quinlan
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=20210503185639.GA993318@bjorn-Precision-5520 \
--to=helgaas@kernel.org \
--cc=aouledameur@baylibre.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=james.quinlan@broadcom.com \
--cc=jim2101024@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=nsaenzjulienne@suse.de \
--cc=p.zabel@pengutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).