From: Andrew Lunn <andrew@lunn.ch>
To: KAVYA M M <kavyamadarsh@gmail.com>
Cc: Prasanth <prasanth.padarthi10@gmail.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
openbmc@lists.ozlabs.org, joel@jms.id.au,
andrew@codeconstruct.com.au, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org
Subject: Re: [PATCH v8 2/2] ARM: dts: aspeed: Add ASRock Rack B650D4U BMC
Date: Mon, 26 Oct 2026 13:36:30 +0100 [thread overview]
Message-ID: <e33a471b-5f4f-492f-9656-e19e0dbfa1b7@lunn.ch> (raw)
In-Reply-To: <CAD_a9mYKSYyP2TqeyjbQWYHdZgF3ggdrU6oTK6VWs2C2GSYMjQ@mail.gmail.com>
On Mon, Oct 26, 2026 at 10:04:05AM +0530, KAVYA M M wrote:
> Hello team,
> I am new to OpenBMC. I want to development image for the machine using the
> OpenBMC/Yocto build system, available firmware information, and readings from
> the existing BMC.
FYI
It is considered bad practice to hijack some other thread for
unrelated matters. Please start a new thread.
Also, don't top post. Netiquette rules apply to mailing lists.
Andrew
prev parent reply other threads:[~2026-10-26 12:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 6:29 [PATCH v8 0/2] ARM: dts: aspeed: Add ASRock Rack B650D4U BMC support Prasanth Kumar Padarthi
2026-10-02 6:29 ` [PATCH v8 1/2] dt-bindings: arm: aspeed: Add ASRock Rack B650D4U Prasanth Kumar Padarthi
2026-10-02 6:29 ` [PATCH v8 2/2] ARM: dts: aspeed: Add ASRock Rack B650D4U BMC Prasanth Kumar Padarthi
2026-10-26 3:34 ` Prasanth
[not found] ` <CAD_a9mYKSYyP2TqeyjbQWYHdZgF3ggdrU6oTK6VWs2C2GSYMjQ@mail.gmail.com>
2026-10-26 12:36 ` Andrew Lunn [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=e33a471b-5f4f-492f-9656-e19e0dbfa1b7@lunn.ch \
--to=andrew@lunn.ch \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=kavyamadarsh@gmail.com \
--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=openbmc@lists.ozlabs.org \
--cc=prasanth.padarthi10@gmail.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®