From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] pinctrl: Kconfig: remove duplicated nodes
Date: Mon, 21 Oct 2019 13:26:09 -0400 [thread overview]
Message-ID: <20191021172609.GQ11173@bill-the-cat> (raw)
In-Reply-To: <20191021130754.32466-1-patrick.delaunay@st.com>
On Mon, Oct 21, 2019 at 03:07:54PM +0200, Patrick Delaunay wrote:
> Remove the duplicated configs introduced when the same patch is
> applied twice times:
> - commit e878b53a79d1 ("dm: pinctrl: introduce PINCONF_RECURSIVE
> option")
> - commit c20851b3d850 ("dm: pinctrl: introduce PINCONF_RECURSIVE
> option")
>
>
> Signed-off-by: Patrick Delaunay <patrick.delaunay@st.com>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20191021/cb3ae99d/attachment.sig>
next prev parent reply other threads:[~2019-10-21 17:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 13:07 [U-Boot] [PATCH] pinctrl: Kconfig: remove duplicated nodes Patrick Delaunay
2019-10-21 15:44 ` Anatolij Gustschin
2019-10-21 17:26 ` Tom Rini [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-22 7:51 Patrick DELAUNAY
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=20191021172609.GQ11173@bill-the-cat \
--to=trini@konsulko.com \
--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