From: Dawid Glazik <dawid.glazik@linux.intel.com>
To: Andrew Jeffery <andrew@codeconstruct.com.au>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
maciej.lawniczak@intel.com
Subject: Re: [PATCH v3 0/3] arm: dts: aspeed: add Intel AVCRP and JNCRP BMC platforms
Date: Fri, 23 Oct 2026 11:20:45 +0200 [thread overview]
Message-ID: <9561c180-ff8d-489d-9ad1-8d9a7afb592c@linux.intel.com> (raw)
In-Reply-To: <fb048449033e125df93c2925d6dccafbd4114685.camel@codeconstruct.com.au>
Hi Andrew,
On 10/23/2026 6:17 AM, Andrew Jeffery wrote:
> Hi Dawid,
>
> On Wed, 2026-10-21 at 22:26 +0200, Dawid Glazik wrote:
>> This series adds initial upstream support for the Intel AVCRP and JNCRP
>> BMC platforms based on the ASPEED AST2600.
>>
>> The first patch adds the board compatibles to the ASPEED binding. The
>> remaining two patches add the board DTS files and register them in the
>> ASPEED DTB build list.
>>
>> Dawid Glazik (3):
>> dt-bindings: arm: aspeed: Add Intel AVCRP and JNCRP boards
>> ARM: dts: aspeed: add Intel AVCRP BMC
>> ARM: dts: aspeed: add Intel JNCRP BMC
>>
>> .../bindings/arm/aspeed/aspeed.yaml | 2 +
>> arch/arm/boot/dts/aspeed/Makefile | 2 +
>> .../dts/aspeed/aspeed-bmc-intel-avcrp.dts | 322 ++++++++++++++++++
>> .../dts/aspeed/aspeed-bmc-intel-jncrp.dts | 276 +++++++++++++++
>> 4 files changed, 602 insertions(+)
>> create mode 100644 arch/arm/boot/dts/aspeed/aspeed-bmc-intel-avcrp.dts
>> create mode 100644 arch/arm/boot/dts/aspeed/aspeed-bmc-intel-jncrp.dts
>>
>>
>> base-commit: e7ae89a0c97ce2b68b0983cd01eda67cf373517d
>
> Can you please discuss why you based this series on v7.1-rc5? v7.3 has
> been released, v7.1-rc5 is a long time ago.
>
> In the future please base changes for the AST2600 on the latest -rc1,
> or the aspeed/arm/dt branch of bmc/linux.git on git.kernel.org.
>
That's my mistake. I'll rebase onto aspeed/arm/dt of bmc/linux.git and
send v4. For future AST2600 changes I'll use that branch as the base.
>> prerequisite-patch-id: 23091b539ec7723a865d82da7703bf70c6ed0222
>
> Can you please rebase this patch to send it to Lee on its own. The
> AST2600-based platforms currently generate a warning without it. I had
> hoped Lee would apply it in the same cycle.
Sure, I will reach out to him.
Regards,
Dawid
prev parent reply other threads:[~2026-10-23 9:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 20:26 Dawid Glazik
2026-10-21 20:26 ` [PATCH v3 1/3] dt-bindings: arm: aspeed: Add Intel AVCRP and JNCRP boards Dawid Glazik
2026-10-21 20:26 ` [PATCH v3 2/3] ARM: dts: aspeed: add Intel AVCRP BMC Dawid Glazik
2026-10-21 20:26 ` [PATCH v3 3/3] ARM: dts: aspeed: add Intel JNCRP BMC Dawid Glazik
2026-10-23 4:17 ` [PATCH v3 0/3] arm: dts: aspeed: add Intel AVCRP and JNCRP BMC platforms Andrew Jeffery
2026-10-23 9:20 ` Dawid Glazik [this message]
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=9561c180-ff8d-489d-9ad1-8d9a7afb592c@linux.intel.com \
--to=dawid.glazik@linux.intel.com \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.lawniczak@intel.com \
--cc=robh@kernel.org \
/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
all inboxes | Powered by JetHome®