All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Patrice CHOTARD <patrice.chotard@foss.st.com>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
	Patrick DELAUNAY <patrick.delaunay@foss.st.com>,
	Christophe KERELLO <christophe.kerello@foss.st.com>
Subject: Re: [PULL] Pull request for u-boot next / v2022.10 = u-boot-stm32-20220927
Date: Tue, 27 Sep 2022 09:53:17 -0400	[thread overview]
Message-ID: <20220927135317.GP3044094@bill-the-cat> (raw)
In-Reply-To: <f9418263-e459-747b-60ef-12bd247c8730@foss.st.com>

[-- Attachment #1: Type: text/plain, Size: 859 bytes --]

On Tue, Sep 27, 2022 at 02:00:14PM +0200, Patrice CHOTARD wrote:

> Hi Tom,
> 
> Please pull the STM32 related fixes for u-boot/next, v2022.10: u-boot-stm32-20220927 
> 
> CI status: https://source.denx.de/u-boot/custodians/u-boot-stm/-/pipelines/13610
> 
> Thanks
> Patrice
> 
> The following changes since commit ebdd6afa543324648138f780a648b8fb65d488eb:
> 
>   Merge branch 'next' of https://source.denx.de/u-boot/custodians/u-boot-marvell into next (2022-09-20 08:50:07 -0400)
> 
> are available in the Git repository at:
> 
>   https://source.denx.de/u-boot/custodians/u-boot-stm.git tags/u-boot-stm32-20220927
> 
> for you to fetch changes up to 762d410e0db94c41b8d7f1ec85e47f7474655ad8:
> 
>   configs: increase SYS_MALLOC_F_LEN for STM32 MCU's board (2022-09-27 10:41:02 +0200)
> 

Applied to u-boot/next, thanks!

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

      parent reply	other threads:[~2022-09-27 13:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27 12:00 [PULL] Pull request for u-boot next / v2022.10 = u-boot-stm32-20220927 Patrice CHOTARD
2022-09-27 13:06 ` Patrice CHOTARD
2022-09-27 13:53 ` 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=20220927135317.GP3044094@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=christophe.kerello@foss.st.com \
    --cc=patrice.chotard@foss.st.com \
    --cc=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.