From: Tom Rini <trini@konsulko.com>
To: Naresh Solanki <naresh.solanki@9elements.com>
Cc: u-boot@lists.denx.de, "Chia-Wei,
Wang" <chiawei_wang@aspeedtech.com>,
Ryan Chen <ryan_chen@aspeedtech.com>,
Aspeed BMC SW team <BMC-SW@aspeedtech.com>,
Joel Stanley <joel@jms.id.au>,
Patrick Rudolph <patrick.rudolph@9elements.com>
Subject: Re: [PATCH] sbp1: Add support for IBM SBP1 board
Date: Wed, 20 Dec 2023 14:12:11 -0500 [thread overview]
Message-ID: <20231220191211.GO2513409@bill-the-cat> (raw)
In-Reply-To: <20231220091236.1059109-1-naresh.solanki@9elements.com>
[-- Attachment #1: Type: text/plain, Size: 843 bytes --]
On Wed, Dec 20, 2023 at 02:42:24PM +0530, Naresh Solanki wrote:
> From: Patrick Rudolph <patrick.rudolph@9elements.com>
>
> Add defconfig & devicetree for IBM SBP1 board BMC based on AST2600 SoC.
>
> Signed-off-by: Patrick Rudolph <patrick.rudolph@9elements.com>
> Signed-off-by: Naresh Solanki <naresh.solanki@9elements.com>
> ---
>
> Changes:
> - Update MAINTAINERS
> ---
> arch/arm/dts/Makefile | 4 +-
> arch/arm/dts/ast2600-sbp1.dts | 96 ++++++++++++++++++++
> board/aspeed/evb_ast2600/MAINTAINERS | 1 +
> configs/ibm-sbp1_defconfig | 126 +++++++++++++++++++++++++++
> 4 files changed, 226 insertions(+), 1 deletion(-)
> create mode 100644 arch/arm/dts/ast2600-sbp1.dts
> create mode 100644 configs/ibm-sbp1_defconfig
Is this device tree submitted upstream?
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-12-20 19:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 9:12 [PATCH] sbp1: Add support for IBM SBP1 board Naresh Solanki
2023-12-20 19:12 ` Tom Rini [this message]
2023-12-20 21:08 ` Naresh Solanki
2023-12-20 22:38 ` Tom Rini
2024-01-02 9:29 ` Patrick Rudolph
2024-01-03 1:51 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2023-11-17 10:50 Naresh Solanki
2023-11-23 0:53 ` Tom Rini
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=20231220191211.GO2513409@bill-the-cat \
--to=trini@konsulko.com \
--cc=BMC-SW@aspeedtech.com \
--cc=chiawei_wang@aspeedtech.com \
--cc=joel@jms.id.au \
--cc=naresh.solanki@9elements.com \
--cc=patrick.rudolph@9elements.com \
--cc=ryan_chen@aspeedtech.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