From: Tom Rini <trini@konsulko.com>
To: Marek Vasut <marex@denx.de>
Cc: "u-boot@lists.denx.de" <u-boot@lists.denx.de>
Subject: Re: [PULL] u-boot-socfpga/master
Date: Mon, 28 Mar 2022 17:04:21 -0400 [thread overview]
Message-ID: <20220328210421.GK14476@bill-the-cat> (raw)
In-Reply-To: <b6b2950b-1106-63e8-b4b4-71e378f626f8@denx.de>
[-- Attachment #1: Type: text/plain, Size: 567 bytes --]
On Mon, Mar 28, 2022 at 10:05:39PM +0200, Marek Vasut wrote:
> One-liner env fix below.
>
> The following changes since commit e893e8ea6a5d3af312747d00f93587559193a426:
>
> Prepare v2022.04-rc5 (2022-03-28 10:14:51 -0400)
>
> are available in the Git repository at:
>
> git://git.denx.de/u-boot-socfpga.git master
>
> for you to fetch changes up to 25cff0c1fa83e149e4693121f8b5e287659eed71:
>
> arm: socfpga: vining: Fix mtdparts for 2x256 MiB SF variant (2022-03-28
> 21:49:03 +0200)
>
Applied to u-boot/master, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-03-28 21:04 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 20:05 [PULL] u-boot-socfpga/master Marek Vasut
2022-03-28 21:04 ` Tom Rini [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-22 1:04 Marek Vasut
2023-02-22 22:51 ` Tom Rini
2022-05-23 21:50 Marek Vasut
2022-05-24 15:51 ` Tom Rini
2021-09-22 22:36 Marek Vasut
2021-09-23 21:20 ` Tom Rini
2020-06-14 15:28 Marek Vasut
2020-06-15 13:33 ` Tom Rini
2020-04-28 11:53 Marek Vasut
2020-04-28 16:11 ` Tom Rini
2020-04-13 20:02 Marek Vasut
2020-04-14 23:24 ` Tom Rini
2020-03-31 3:24 Marek Vasut
2020-03-31 19:09 ` Tom Rini
2020-03-04 12:23 Marek Vasut
2020-03-04 23:51 ` Tom Rini
2020-02-02 17:18 Marek Vasut
2020-02-02 20:26 ` Tom Rini
2020-02-03 8:24 ` Marek Vasut
2020-02-03 8:47 ` Marek Vasut
2020-02-04 4:13 ` Tom Rini
2020-02-05 6:58 ` Marek Vasut
2020-02-07 18:51 ` Tom Rini
2020-01-08 15:31 Marek Vasut
2020-01-08 23:55 ` 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=20220328210421.GK14476@bill-the-cat \
--to=trini@konsulko.com \
--cc=marex@denx.de \
--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.