From: Joel Stanley <joel@jms.id.au>
To: Zev Weiss <zev@bewilderbeest.net>
Cc: openbmc@lists.ozlabs.org
Subject: Re: [PATCH linux dev-6.5 0/4] Add device trees for ASrock E3C256D4I & SPC621D8HM3
Date: Wed, 6 Dec 2023 17:17:08 +1030 [thread overview]
Message-ID: <CACPK8XeXqgonvj5WQfx+ov8o5OrABLHXDqs3ST27ij59yC67yA@mail.gmail.com> (raw)
In-Reply-To: <20231206023742.5242-6-zev@bewilderbeest.net>
On Wed, 6 Dec 2023 at 13:07, Zev Weiss <zev@bewilderbeest.net> wrote:
>
> Hello,
>
> These patches add support for the BMCs on the ASRock e3c256d4i and
> spc621d8hm3 boards. All four patches are currently in the 'for-next'
> branch of Joel's bmc.git tree. I used the '-x' flag when
> cherry-picking them onto the dev-6.5 branch, but since they're not yet
> actually merged into the mainline kernel I suppose it's possible the
> upstream commit hashes might still change, so feel free to drop those
> tags as preferred.
>
> [Mistakenly didn't CC the list on first send, apologies for the
> duplication Joel & Andrew.]
I've merged these on top of the shiny new 6.6 tree.
Cheers,
Joel
prev parent reply other threads:[~2023-12-06 6:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 2:37 [PATCH linux dev-6.5 0/4] Add device trees for ASrock E3C256D4I & SPC621D8HM3 Zev Weiss
2023-12-06 2:37 ` [PATCH linux dev-6.5 1/4] dt-bindings: arm: aspeed: document ASRock SPC621D8HM3 Zev Weiss
2023-12-06 2:37 ` [PATCH linux dev-6.5 2/4] ARM: dts: aspeed: Add ASRock SPC621D8HM3 BMC Zev Weiss
2023-12-06 2:37 ` [PATCH linux dev-6.5 3/4] dt-bindings: arm: aspeed: document ASRock E3C256D4I Zev Weiss
2023-12-06 2:37 ` [PATCH linux dev-6.5 4/4] ARM: dts: aspeed: Add ASRock E3C256D4I BMC Zev Weiss
2023-12-06 6:47 ` Joel Stanley [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=CACPK8XeXqgonvj5WQfx+ov8o5OrABLHXDqs3ST27ij59yC67yA@mail.gmail.com \
--to=joel@jms.id.au \
--cc=openbmc@lists.ozlabs.org \
--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).