From: Tom Rini <trini@konsulko.com>
To: "Peng Fan" <peng.fan@nxp.com>, "Marek Behún" <kabel@kernel.org>
Cc: "u-boot@lists.denx.de" <u-boot@lists.denx.de>,
"pali@kernel.org" <pali@kernel.org>,
Sean Anderson <sean.anderson@seco.com>
Subject: Re: [GIT PULL] please pull fsl-qoriq-2022-9-7
Date: Wed, 7 Sep 2022 13:55:46 -0400 [thread overview]
Message-ID: <20220907175546.GO7942@bill-the-cat> (raw)
In-Reply-To: <DU0PR04MB94174DAABD60EAADF7E9496488419@DU0PR04MB9417.eurprd04.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 2385 bytes --]
On Wed, Sep 07, 2022 at 12:38:10PM +0000, Peng Fan wrote:
> Hi Tom,
>
> Please pull fsl-qoriq-2022-9-7
>
> Sorry for the quick rush just after fsl-qoriq-2022-9-6:
> Pali's patch not in my patchwork, got missed.
> Sean's patch pending for sometime, I just fix conflict when
> apply Sean's patch, so pick up.
>
> ---------------------------------------
> p1_p2_rdb_pc board update
> net: fm: Verify Fman microcode
> ---------------------------------------
>
> CI: https://source.denx.de/u-boot/custodians/u-boot-fsl-qoriq/-/pipelines/13377
>
> Thanks,
> Peng.
>
> The following changes since commit 59c51fa4abbca41d2a4d60c0fe4d8f05fc83fb46:
>
> Merge https://source.denx.de/u-boot/custodians/u-boot-riscv (2022-09-06 09:01:39 -0400)
>
> are available in the Git repository at:
>
> https://source.denx.de/u-boot/custodians/u-boot-fsl-qoriq.git tags/fsl-qoriq-2022-9-7
>
> for you to fetch changes up to 857e313a3d44618e09fc64816fd5e561e2189ab7:
>
> net: fm: Add support for FIT firmware (2022-09-07 13:44:55 +0800)
>
> ----------------------------------------------------------------
> Pali Rohár (3):
> board: freescale: p1_p2_rdb_pc: Add env commands norlowerboot, norupperboot, sd2boot and defboot
> board: freescale: p1_p2_rdb_pc: Delete watchdog max6370 node in load_default mode
> board: freescale: p1_p2_rdb_pc: Calculate offsets for eSDHC boot sector
>
> Sean Anderson (6):
> ARMv8/sec_firmware: Remove SEC_FIRMWARE_FIT_CNF_NAME
> image: fit: Add some helpers for getting data
> ARMv8/sec_firmware: Convert to use fit_get_data_conf_prop
> cmd: fpga: Convert to use fit_get_data_node
> net: Convert fit verification to use fit_get_data_*
> net: fm: Add support for FIT firmware
First, I've applied this now to u-boot/master.
But second, the reason Pali's patches were assigned to someone else,
Marek, was because of the total lack of response these last several
months. Marek was added for the subset of PowerPC platforms that he and
Pali have an interest in, which is all around the Turris 1.x router
platform.
So, what do you think about how to proceed here moving forward? A large
number of Pali's changes have been waiting to be picked up / reviewed
for a very long time, is why we've added Marek, to cover the Turris
platform.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-09-07 17:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 12:38 [GIT PULL] please pull fsl-qoriq-2022-9-7 Peng Fan
2022-09-07 17:55 ` Tom Rini [this message]
2022-09-07 23:21 ` Peng Fan
2022-09-08 15:05 ` Pali Rohár
2022-09-08 16:29 ` Marek Behún
2022-09-12 7:33 ` Peng Fan
2022-09-12 7:37 ` Peng Fan
2022-09-16 15:58 ` Marek Behún
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=20220907175546.GO7942@bill-the-cat \
--to=trini@konsulko.com \
--cc=kabel@kernel.org \
--cc=pali@kernel.org \
--cc=peng.fan@nxp.com \
--cc=sean.anderson@seco.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.