From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Dawid Glazik <dawid.glazik@linux.intel.com>,
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 v4 0/3] arm: dts: aspeed: add Intel AVCRP and JNCRP BMC platforms
Date: Fri, 06 Nov 2026 15:10:00 +1030 [thread overview]
Message-ID: <d7a1f55d822af84b00591a57d2bbc1541c184412.camel@codeconstruct.com.au> (raw)
In-Reply-To: <cover.1792749922.git.dawid.glazik@linux.intel.com>
On Mon, 2026-10-26 at 17:40 +0100, 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.
>
> Changes in v4:
> - Rebased onto aspeed/arm/dt of bmc/linux.git. No other changes.
>
> 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
Bit of a nitpick, however, I have other requests on the relevant
patches:
For both of the latter commits, can you please capitalise the first
word after the prefix list (in this case, 'Add')?
Andrew
prev parent reply other threads:[~2026-11-06 4:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 16:40 Dawid Glazik
2026-10-26 16:40 ` [PATCH v4 1/3] dt-bindings: arm: aspeed: Add Intel AVCRP and JNCRP boards Dawid Glazik
2026-10-26 16:40 ` [PATCH v4 2/3] ARM: dts: aspeed: add Intel AVCRP BMC Dawid Glazik
2026-11-06 4:44 ` Andrew Jeffery
2026-10-26 16:40 ` [PATCH v4 3/3] ARM: dts: aspeed: add Intel JNCRP BMC Dawid Glazik
2026-11-06 4:50 ` Andrew Jeffery
2026-11-06 4:40 ` Andrew Jeffery [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=d7a1f55d822af84b00591a57d2bbc1541c184412.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=dawid.glazik@linux.intel.com \
--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®