All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peng Fan <peng.fan@oss.nxp.com>
To: "Marek Behún" <kabel@kernel.org>, "Pali Rohár" <pali@kernel.org>,
	"Peng Fan" <peng.fan@nxp.com>
Cc: Tom Rini <trini@konsulko.com>,
	"u-boot@lists.denx.de" <u-boot@lists.denx.de>,
	Sean Anderson <sean.anderson@seco.com>
Subject: Re: [GIT PULL] please pull fsl-qoriq-2022-9-7
Date: Mon, 12 Sep 2022 15:33:05 +0800	[thread overview]
Message-ID: <720674ae-3ec7-4e84-ef79-d6890318b25f@oss.nxp.com> (raw)
In-Reply-To: <20220908182955.5ce12130@dellmb>



On 9/9/2022 12:29 AM, Marek Behún wrote:
> On Thu, 8 Sep 2022 17:05:53 +0200
> Pali Rohár <pali@kernel.org> wrote:
> 
>> On Thursday 08 September 2022 07:21:03 Peng Fan wrote:
>>> On 9/8/2022 1:55 AM, Tom Rini wrote:
>>>> 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.
>>>
>>> If the delay was caused by me, sorry for that. I could ramp up more
>>> time in maintainer work.
>>>
>>> Pali,
>>>
>>> I am ok if Turris patches go through Marek's tree. or you wanna me to
>>> pick up those patches, please help assign those patches. If bug fix,
>>> I could prepare PR to master branch, if new feature, we could consider PR
>>> for next branch.
>>>
>>> Thanks,
>>> Peng.
>>
>> Here is the list of currently waiting patches which are not in master branch yet:
>>
>> https://patchwork.ozlabs.org/project/uboot/patch/20220801154220.20068-1-pali@kernel.org/
>> https://patchwork.ozlabs.org/project/uboot/patch/20220801154220.20068-2-pali@kernel.org/
>> https://patchwork.ozlabs.org/project/uboot/patch/20220803112049.4287-1-pali@kernel.org/
>> https://patchwork.ozlabs.org/project/uboot/patch/20220805200941.22101-1-pali@kernel.org/
>> https://patchwork.ozlabs.org/project/uboot/patch/20220805200941.22101-2-pali@kernel.org/
>> https://patchwork.ozlabs.org/project/uboot/patch/20220805200941.22101-3-pali@kernel.org/
>> https://patchwork.ozlabs.org/project/uboot/patch/20220803215655.2361-1-pali@kernel.org/
>> https://patchwork.ozlabs.org/project/uboot/patch/20220803112442.4735-1-pali@kernel.org/
>> https://patchwork.ozlabs.org/project/uboot/patch/20220819092001.15045-1-pali@kernel.org/
>> https://patchwork.ozlabs.org/project/uboot/patch/20220815080140.4048-1-pali@kernel.org/
> 
> I am working on this, will give more info soon.

Sorry, I not follow, you mean new version patches or else?

Thanks,
Peng.

> 
> Marek

  reply	other threads:[~2022-09-12  7:33 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
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 [this message]
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=720674ae-3ec7-4e84-ef79-d6890318b25f@oss.nxp.com \
    --to=peng.fan@oss.nxp.com \
    --cc=kabel@kernel.org \
    --cc=pali@kernel.org \
    --cc=peng.fan@nxp.com \
    --cc=sean.anderson@seco.com \
    --cc=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 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.