public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.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 07:56:55 -0500	[thread overview]
Message-ID: <20210106125655.GP2292@bill-the-cat> (raw)
In-Reply-To: <e362403d-b543-cd5c-1edb-41aa3afba728@foss.st.com>

On Wed, Jan 06, 2021 at 01:12:26PM +0100, Patrick DELAUNAY wrote:

> 
> 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)
> 

Applied to u-boot/master, thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20210106/d53fce64/attachment.sig>

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-06 12:12 [PULL] Pull request for u-boot master / v2021.01 = u-boot-stm32-20210106 Patrick DELAUNAY
2021-01-06 12:56 ` Tom Rini [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=20210106125655.GP2292@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