From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PULL] Pull request: u-boot-stm32 for v2020.10= u-boot-stm32-20200909
Date: Wed, 9 Sep 2020 15:45:20 -0400 [thread overview]
Message-ID: <20200909194520.GS7259@bill-the-cat> (raw)
In-Reply-To: <83458f7b5f104d0f94f243f10f0d7060@SFHDAG6NODE3.st.com>
On Wed, Sep 09, 2020 at 03:20:27PM +0000, Patrick DELAUNAY wrote:
> Hi Tom,
>
> Please pull the STM32 related patches for v2020.10: u-boot-stm32-20200528
>
> With the following changes:
> - fixes on AV96 board: pull up on UART4 RX and adjust PLL4
>
> CI status:
> https://gitlab.denx.de/u-boot/custodians/u-boot-stm/-/pipelines/4631
>
> Thanks,
> Patrick
>
> git request-pull origin/master https://gitlab.denx.de/u-boot/custodians/u-boot-stm.git u-boot-stm32-20200909
>
> The following changes since commit 96d66a9b8ce11aae9f8bef5244b83b4740b37644:
>
> Prepare v2020.10-rc4 (2020-09-07 14:17:33 -0400)
>
> are available in the Git repository at:
>
> https://gitlab.denx.de/u-boot/custodians/u-boot-stm.git tags/u-boot-stm32-20200909
>
> for you to fetch changes up to b6055945d66d0f4e3b1ecb82af476232067a4ee4:
>
> ARM: dts: stm32: Adjust PLL4 settings on AV96 again (2020-09-09 15:02:23 +0200)
>
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/20200909/92c54cb4/attachment.sig>
next prev parent reply other threads:[~2020-09-09 19:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 15:20 [PULL] Pull request: u-boot-stm32 for v2020.10= u-boot-stm32-20200909 Patrick DELAUNAY
2020-09-09 19:45 ` Tom Rini [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-09 14:57 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=20200909194520.GS7259@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