From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] dm: pinctrl: fix for introduce PINCONF_RECURSIVE option
Date: Mon, 21 Oct 2019 20:09:10 +0200 [thread overview]
Message-ID: <20191021200910.2903a235@crub> (raw)
In-Reply-To: <c7cf2c4dbaa245dfa80caa9af22dd98f@SFHDAG6NODE3.st.com>
Hi Patrick,
On Mon, 21 Oct 2019 17:10:21 +0000
Patrick DELAUNAY patrick.delaunay at st.com wrote:
...
> I check deeper today the root cause of the issue and I have a clean solution
> with v2 patch: http://patchwork.ozlabs.org/patch/1180575/
>
> The friday patch wasn't enough at least for my board, but ok for sandbox.
OK, thanks for fixing it!
--
Anatolij
prev parent reply other threads:[~2019-10-21 18:09 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
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 [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=20191021200910.2903a235@crub \
--to=agust@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