All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick DELAUNAY <patrick.delaunay@foss.st.com>
To: u-boot@lists.denx.de
Subject: [PULL] Pull request for u-boot master / v2021.01 = u-boot-stm32-20210106
Date: Wed, 6 Jan 2021 13:12:26 +0100	[thread overview]
Message-ID: <e362403d-b543-cd5c-1edb-41aa3afba728@foss.st.com> (raw)


Hi Tom,

Please pull the latest STM32 related patches for u-boot/master, 
v2021.01: u-boot-stm32-20210106

- Fix GPIO hog flags on DHCOM boards

CI status: 
https://gitlab.denx.de/u-boot/custodians/u-boot-stm/-/pipelines/5764

Thanks,
Patrick

git request-pull origin/master 
https://gitlab.denx.de/u-boot/custodians/u-boot-stm.git 
u-boot-stm32-20210106

The following changes since commit 62b07b5173e3d04fabfac42cf1f4779d021f94ad:

 ? Prepare v2021.01-rc5 (2021-01-05 07:30:39 -0500)

are available in the Git repository at:

 ? https://gitlab.denx.de/u-boot/custodians/u-boot-stm.git 
tags/u-boot-stm32-20210106

for you to fetch changes up to ec4efd5ae724c51cf40437fa4c6bd758d3816bcd:

 ? ARM: dts: stm32: Fix GPIO hog flags on DHCOM DRC02 (2021-01-06 
11:01:31 +0100)

----------------------------------------------------------------
- Fix GPIO hog flags on DHCOM boards

----------------------------------------------------------------
Marek Vasut (2):
 ????? ARM: dts: stm32: Fix GPIO hog flags on DHCOM PicoITX
 ????? ARM: dts: stm32: Fix GPIO hog flags on DHCOM DRC02

 ?arch/arm/dts/stm32mp15xx-dhcom-drc02.dts?? | 4 ++--
 ?arch/arm/dts/stm32mp15xx-dhcom-picoitx.dts | 2 +-
 ?2 files changed, 3 insertions(+), 3 deletions(-)

             reply	other threads:[~2021-01-06 12:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-06 12:12 Patrick DELAUNAY [this message]
2021-01-06 12:56 ` [PULL] Pull request for u-boot master / v2021.01 = u-boot-stm32-20210106 Tom Rini

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=e362403d-b543-cd5c-1edb-41aa3afba728@foss.st.com \
    --to=patrick.delaunay@foss.st.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.