From: Chanh Nguyen <chanh@amperemail.onmicrosoft.com>
To: "Andrew Jeffery" <andrew@codeconstruct.com.au>,
"Chanh Nguyen" <chanh@os.amperecomputing.com>,
u-boot@lists.denx.de,
"Albert Aribaud" <albert.u.boot@aribaud.net>,
"Joel Stanley" <joel@jms.id.au>,
"Zev Weiss" <zev@bewilderbeest.net>,
"Andrew Jeffery" <andrew@aj.id.au>,
"Cédric Le Goater" <clg@kaod.org>,
"Jae Hyun Yoo" <quic_jaehyoo@quicinc.com>,
"Patrick Rudolph" <patrick.rudolph@9elements.com>,
"Dylan Hung" <dylan_hung@aspeedtech.com>,
"Graeme Gregory" <quic_ggregory@quicinc.com>,
"Eddie James" <eajames@linux.ibm.com>,
"OpenBMC Maillist" <openbmc@lists.ozlabs.org>,
"Open Source Submission" <patches@amperecomputing.com>
Cc: Thang Nguyen <thang@os.amperecomputing.com>,
Phong Vo <phong@os.amperecomputing.com>,
Quan Nguyen <quan@os.amperecomputing.com>
Subject: Re: [PATCH u-boot v2019.04-aspeed-openbmc] ARM: dts: aspeed: Add Ampere's BMC platform (AST2600)
Date: Mon, 25 Mar 2024 17:18:25 +0700 [thread overview]
Message-ID: <642c4474-1b14-4095-b080-e467dc0230ba@amperemail.onmicrosoft.com> (raw)
In-Reply-To: <2a55a4544f3c1c9b31ecf5232a8d8409a87a6f2a.camel@codeconstruct.com.au>
On 25/03/2024 12:32, Andrew Jeffery wrote:
> Hi Chanh,
>
> On Tue, 2024-03-19 at 14:21 +0700, Chanh Nguyen wrote:
>> Add the initial version of the device tree for the Ampere BMC
>> platform, which is equipped with the Aspeed AST2600 BMC SoC.
>>
>> Signed-off-by: Chanh Nguyen <chanh@os.amperecomputing.com>
>> ---
>> arch/arm/dts/Makefile | 1 +
>> arch/arm/dts/ast2600-ampere.dts | 113 ++++++++++++++++++++++++++++++++
>> 2 files changed, 114 insertions(+)
>> create mode 100644 arch/arm/dts/ast2600-ampere.dts
>>
>> diff --git a/arch/arm/dts/Makefile b/arch/arm/dts/Makefile
>> index 37675a3277..3642d59c89 100755
>> --- a/arch/arm/dts/Makefile
>> +++ b/arch/arm/dts/Makefile
>> @@ -691,6 +691,7 @@ dtb-$(CONFIG_ARCH_ASPEED) += \
>> ast2600-greatlakes.dtb \
>> ast2600-intel.dtb \
>> ast2600-ncsi.dtb \
>> + ast2600-ampere.dtb \
>> ast2600-p10bmc.dtb \
>> ast2600-pfr.dtb \
>> ast2600-qcom-dc-scm-v1.dtb \
>
> Given this hunk and the tags in the `[PATCH]` prefix of the mail
> subject you've based this change on OpenBMC's fork of u-boot, which is
> heavily (out of date, and) inspired by Aspeed's SDK tree. I've applied
> this to OpenBMC's fork for now.
>
Thank Andrew! I saw my patch on the OpenBMC's fork.
> However, you've sent this to the upstream list. You will need to rework
> your patch on top of mainline u-boot if you want it accepted there, and
> follow all the usual documentation on how to submit patches to the u-
> boot project (e.g. you should not be including `u-boot v2019.04-aspeed-
> openbmc` in the patch subject prefix in upstream submissions).
>
> Andrew
Sorry all! It is my mistake. I just want to send this to OpenBMC's fork,
but I used the upstream mail list.
next prev parent reply other threads:[~2024-03-25 10:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 7:21 [PATCH u-boot v2019.04-aspeed-openbmc] ARM: dts: aspeed: Add Ampere's BMC platform (AST2600) Chanh Nguyen
2024-03-25 5:32 ` Andrew Jeffery
2024-03-25 10:18 ` Chanh Nguyen [this message]
[not found] <20231210042508.16187-1-chanh@os.amperecomputing.com>
2024-01-04 4:19 ` Chanh Nguyen
2024-01-22 3:08 ` Chanh Nguyen
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=642c4474-1b14-4095-b080-e467dc0230ba@amperemail.onmicrosoft.com \
--to=chanh@amperemail.onmicrosoft.com \
--cc=albert.u.boot@aribaud.net \
--cc=andrew@aj.id.au \
--cc=andrew@codeconstruct.com.au \
--cc=chanh@os.amperecomputing.com \
--cc=clg@kaod.org \
--cc=dylan_hung@aspeedtech.com \
--cc=eajames@linux.ibm.com \
--cc=joel@jms.id.au \
--cc=openbmc@lists.ozlabs.org \
--cc=patches@amperecomputing.com \
--cc=patrick.rudolph@9elements.com \
--cc=phong@os.amperecomputing.com \
--cc=quan@os.amperecomputing.com \
--cc=quic_ggregory@quicinc.com \
--cc=quic_jaehyoo@quicinc.com \
--cc=thang@os.amperecomputing.com \
--cc=u-boot@lists.denx.de \
--cc=zev@bewilderbeest.net \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).