From: Giulio Benetti <giulio.benetti@benettiengineering.com>
To: Stanley Chu <stanley.chuys@gmail.com>, Tom Rini <trini@konsulko.com>
Cc: kwliu@nuvoton.com, ctcchien@nuvoton.com, avifishman70@gmail.com,
tmaimon77@gmail.com, u-boot@lists.denx.de
Subject: Re: [PATCH v1 1/9] arm: nuvoton: Add support for Nuvoton NPCM845 BMC
Date: Fri, 11 Mar 2022 02:07:35 +0100 [thread overview]
Message-ID: <02184de5-17d9-084d-ee94-7f5862ac6e30@benettiengineering.com> (raw)
In-Reply-To: <9908774c-ba00-1ce4-22f5-82ea81369826@benettiengineering.com>
On 11/03/22 02:06, Giulio Benetti wrote:
> Hi Stanley,
>
> On 11/03/22 01:50, Stanley Chu wrote:
>> Hi Giulio,
>>
>> Thank you for your comment, I've submitted a clk driver patch to address this.
>> https://patchwork.ozlabs.org/project/uboot/patch/20220225075954.3965-1-yschu@nuvoton.com/
>
> Good to see that!
>
> But I think you should submit the entire patchset:
> https://patchwork.ozlabs.org/project/uboot/list/?series=276836&state=%2A&archive=both
>
> including this patch as V2. Otherwise it's difficult to test it.
>
> As you see in Patchwork you have superseded and changes requested on
> other patches. So you should modify them accordingly and send V2 series.
> If other patches have been applied then send only the ones not applied.
> But as I can see here they are still not applied.
Ah, forgotten to mention, please add me and other people involved in
reviewing in Cc for V2.
Thank you!
Best regards
--
Giulio Benetti
Benetti Engineering sas
next prev parent reply other threads:[~2022-03-11 1:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 2:57 [PATCH v1 0/9] Add Nuvoton NPCM845 support Stanley Chu
2021-12-15 2:57 ` [PATCH v1 1/9] arm: nuvoton: Add support for Nuvoton NPCM845 BMC Stanley Chu
2021-12-15 12:12 ` Giulio Benetti
2022-03-11 0:50 ` Stanley Chu
2022-03-11 1:06 ` Giulio Benetti
2022-03-11 1:07 ` Giulio Benetti [this message]
2021-12-15 18:32 ` Sean Anderson
2022-03-11 0:55 ` Stanley Chu
[not found] ` <d23d2925-d5ea-e23b-fb99-7856aedfb328@gmail.com>
[not found] ` <0fee2e28-b3c8-d649-0921-52e6fb098e71@gmail.com>
2022-03-11 0:39 ` Stanley Chu
2022-03-11 0:57 ` Stanley Chu
2022-03-10 18:49 ` Tom Rini
2022-03-11 2:13 ` Stanley Chu
2022-03-11 2:50 ` Tom Rini
2022-03-11 2:53 ` Giulio Benetti
2022-03-11 4:07 ` Stanley Chu
2021-12-15 2:57 ` [PATCH v1 2/9] clk: nuvoton: Add support for NPCM845 Stanley Chu
2021-12-15 18:32 ` Sean Anderson
2022-02-16 16:25 ` Tom Rini
2022-02-17 2:08 ` Stanley
2021-12-15 2:57 ` [PATCH v1 3/9] timer: npcm: Add NPCM timer support Stanley Chu
2021-12-15 2:57 ` [PATCH v1 4/9] serial: npcm: Add support for Nuvoton NPCM SoCs Stanley Chu
2021-12-15 2:57 ` [PATCH v1 5/9] gpio: " Stanley Chu
2021-12-15 2:57 ` [PATCH v1 6/9] pinctrl: nuvoton: Add NPCM8xx pinctrl driver Stanley Chu
2021-12-15 2:57 ` [PATCH v1 7/9] spi: npcm-fiu: add NPCM8xx FIU controller driver Stanley Chu
2021-12-15 2:57 ` [PATCH v1 8/9] ARM: dts: Add Nuvoton NPCM845 device tree Stanley Chu
2021-12-15 13:07 ` Tom Rini
2021-12-15 13:32 ` 盛
2021-12-15 13:35 ` Tom Rini
2021-12-15 15:32 ` Jesse Taube
2021-12-15 15:39 ` Tom Rini
2021-12-15 2:58 ` [PATCH v1 9/9] ARM: configs: Add defconfig for Nuvoton NPCM845 Stanley Chu
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=02184de5-17d9-084d-ee94-7f5862ac6e30@benettiengineering.com \
--to=giulio.benetti@benettiengineering.com \
--cc=avifishman70@gmail.com \
--cc=ctcchien@nuvoton.com \
--cc=kwliu@nuvoton.com \
--cc=stanley.chuys@gmail.com \
--cc=tmaimon77@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox