From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Eddie James <eajames@linux.ibm.com>, linux-aspeed@lists.ozlabs.org
Cc: joel@jms.id.au, devicetree@vger.kernel.org,
linux-fsi@lists.ozlabs.org, robh@kernel.org,
conor+dt@kernel.org, krzk+dt@kernel.org, jk@ozlabs.org,
alistair@popple.id.au, lakshmiy@us.ibm.com
Subject: Re: [PATCH v3 1/3] dt-bindings: fsi: Document the IBM SBEFIFO engine
Date: Fri, 26 Apr 2024 09:35:48 +0930 [thread overview]
Message-ID: <39d0be3341ac886cbe0c201a296e3a899e4eb7b5.camel@codeconstruct.com.au> (raw)
In-Reply-To: <6c2f8ee1-ec59-4ec4-8d0c-507d98225dd6@linux.ibm.com>
On Thu, 2024-04-25 at 16:38 -0500, Eddie James wrote:
> On 4/21/24 18:02, Andrew Jeffery wrote:
> > On Fri, 2024-04-19 at 16:11 -0500, Eddie James wrote:
> > > The SBEFIFO engine provides an interface to the POWER processor
> > > Self Boot Engine (SBE).
> > >
> > > Signed-off-by: Eddie James <eajames@linux.ibm.com>
> > Reviewed-by: Andrew Jeffery <andrew@codeconstruct.com.au>
>
>
> I'm sending this patch in my new series for P11 BMC systems, with an
> additional change for the OCC child nodes. Hopefully that's OK, I kept
> the tags.
From a quick look I think that's fine.
Thanks,
Andrew
next prev parent reply other threads:[~2024-04-26 0:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 21:11 [PATCH v3 0/3] fsi: sbefifo: Prevent async FFDC collection for Odyssey SBEFIFOs Eddie James
2024-04-19 21:11 ` [PATCH v3 1/3] dt-bindings: fsi: Document the IBM SBEFIFO engine Eddie James
2024-04-20 10:54 ` Conor Dooley
2024-04-21 23:02 ` Andrew Jeffery
2024-04-25 21:38 ` Eddie James
2024-04-26 0:05 ` Andrew Jeffery [this message]
2024-04-19 21:11 ` [PATCH v3 2/3] fsi: sbefifo: Prevent async FFDC collection for Odyssey SBEFIFOs Eddie James
2024-04-19 21:11 ` [PATCH v3 3/3] ARM: dts: aspeed: Update Odyssey SBEFIFO compatible strings Eddie James
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=39d0be3341ac886cbe0c201a296e3a899e4eb7b5.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=alistair@popple.id.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.ibm.com \
--cc=jk@ozlabs.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=lakshmiy@us.ibm.com \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-fsi@lists.ozlabs.org \
--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;
as well as URLs for NNTP newsgroup(s).