From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Ninad Palsule <ninad@linux.ibm.com>, minyard@acm.org
Cc: andrew@lunn.ch, brgl@bgdev.pl, linus.walleij@linaro.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
openipmi-developer@lists.sourceforge.net, joel@jms.id.au,
devicetree@vger.kernel.org, eajames@linux.ibm.com,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH v9 1/9] dt-bindings: ipmi: Add binding for IPMB device
Date: Wed, 05 Feb 2025 10:30:53 +1030 [thread overview]
Message-ID: <fd92f75620e48957c2875cdcfd1285c33d3176e6.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20250204194115.3899174-2-ninad@linux.ibm.com>
Hi Corey,
On Tue, 2025-02-04 at 13:41 -0600, Ninad Palsule wrote:
> Add device tree binding document for the IPMB device interface.
> This device is already in use in both driver and .dts files.
>
> Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
> Signed-off-by: Ninad Palsule <ninad@linux.ibm.com>
> ---
> .../devicetree/bindings/ipmi/ipmb-dev.yaml | 56
> +++++++++++++++++++
> 1 file changed, 56 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/ipmi/ipmb-
> dev.yaml
Would you like to take this through the IPMI tree? Otherwise I'm happy
to take it through the BMC tree with your ack.
Andrew
next prev parent reply other threads:[~2025-02-05 0:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 19:41 [PATCH v9 0/9] DTS updates for system1 BMC Ninad Palsule
2025-02-04 19:41 ` [PATCH v9 1/9] dt-bindings: ipmi: Add binding for IPMB device Ninad Palsule
2025-02-05 0:00 ` Andrew Jeffery [this message]
2025-02-27 16:31 ` Corey Minyard
2025-02-04 19:41 ` [PATCH v9 2/9] dt-bindings: gpio: ast2400-gpio: Add hogs parsing Ninad Palsule
2025-02-05 0:02 ` Andrew Jeffery
2025-02-04 19:41 ` [PATCH v9 3/9] ARM: dts: aspeed: system1: Add IPMB device Ninad Palsule
2025-02-04 19:41 ` [PATCH v9 4/9] ARM: dts: aspeed: system1: Add GPIO line name Ninad Palsule
2025-02-04 19:41 ` [PATCH v9 5/9] ARM: dts: aspeed: system1: Reduce sgpio speed Ninad Palsule
2025-02-04 19:41 ` [PATCH v9 6/9] ARM: dts: aspeed: system1: Update LED gpio name Ninad Palsule
2025-02-04 19:41 ` [PATCH v9 7/9] ARM: dts: aspeed: system1: Remove VRs max8952 Ninad Palsule
2025-02-04 19:41 ` [PATCH v9 8/9] ARM: dts: aspeed: system1: Mark GPIO line high/low Ninad Palsule
2025-02-04 19:41 ` [PATCH v9 9/9] ARM: dts: aspeed: system1: Disable gpio pull down Ninad Palsule
2025-02-05 8:40 ` (subset) [PATCH v9 0/9] DTS updates for system1 BMC Bartosz Golaszewski
2025-02-28 6:13 ` Andrew Jeffery
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=fd92f75620e48957c2875cdcfd1285c33d3176e6.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=andrew@lunn.ch \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.ibm.com \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=ninad@linux.ibm.com \
--cc=openipmi-developer@lists.sourceforge.net \
--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).