From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] dm: pinctrl: fix for introduce PINCONF_RECURSIVE option
Date: Fri, 18 Oct 2019 22:25:18 +0200 [thread overview]
Message-ID: <20191018222518.65a61fbc@jawa> (raw)
In-Reply-To: <20191018182922.22960-1-patrick.delaunay@st.com>
On Fri, 18 Oct 2019 20:29:22 +0200
Patrick Delaunay <patrick.delaunay@st.com> wrote:
> Correct the name of the define used in CONFIG_IS_ENABLED():
> it is not align with Kconfig name= CONFIG_$(SPL_)PINCONF_RECURSIVE.
>
> This correct a regression introduced by
> commit c20851b3d850 ("dm: pinctrl: introduce PINCONF_RECURSIVE
> option")
>
> Signed-off-by: Patrick Delaunay <patrick.delaunay@st.com>
> ---
>
> drivers/pinctrl/pinctrl-uclass.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/pinctrl/pinctrl-uclass.c
> b/drivers/pinctrl/pinctrl-uclass.c index 0b1eb7fab4..dc2340b779 100644
> --- a/drivers/pinctrl/pinctrl-uclass.c
> +++ b/drivers/pinctrl/pinctrl-uclass.c
> @@ -157,7 +157,7 @@ static int pinconfig_post_bind(struct udevice
> *dev)
> UCLASS_DRIVER(pinconfig) = {
> .id = UCLASS_PINCONFIG,
> -#if CONFIG_IS_ENABLED(PINCONFIG_RECURSIVE)
> +#if CONFIG_IS_ENABLED(PINCONF_RECURSIVE)
> .post_bind = pinconfig_post_bind,
> #endif
> .name = "pinconfig",
Reviewed-by: Lukasz Majewski <lukma@denx.de>
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20191018/823560ad/attachment.sig>
next prev parent reply other threads:[~2019-10-18 20:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 18:29 [U-Boot] [PATCH] dm: pinctrl: fix for introduce PINCONF_RECURSIVE option Patrick Delaunay
2019-10-18 20:25 ` Lukasz Majewski [this message]
2019-10-19 19:56 ` Anatolij Gustschin
2019-10-19 20:02 ` Anatolij Gustschin
2019-10-21 17:10 ` Patrick DELAUNAY
2019-10-21 18:09 ` Anatolij Gustschin
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=20191018222518.65a61fbc@jawa \
--to=lukma@denx.de \
--cc=u-boot@lists.denx.de \
/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