From: "Rob Herring (Arm)" <robh@kernel.org>
To: Ninad Palsule <ninad@linux.ibm.com>
Cc: pabeni@redhat.com, davem@davemloft.net, edumazet@google.com,
conor+dt@kernel.org, kuba@kernel.org, andrew+netdev@lunn.ch,
joel@jms.id.au, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
krzk+dt@kernel.org, eajames@linux.ibm.com,
andrew@codeconstruct.com.au, minyard@acm.org,
openipmi-developer@lists.sourceforge.net,
devicetree@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v6 02/10] bindings: ipmi: Add binding for IPMB device intf
Date: Thu, 23 Jan 2025 16:12:09 -0600 [thread overview]
Message-ID: <173767032899.448455.5833909744401276024.robh@kernel.org> (raw)
In-Reply-To: <20250116203527.2102742-3-ninad@linux.ibm.com>
On Thu, 16 Jan 2025 14:35:17 -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.
>
> 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
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2025-01-23 22:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 20:35 [PATCH v6 00/10] DTS updates for system1 BMC Ninad Palsule
2025-01-16 20:35 ` [PATCH v6 01/10] dt-bindings: net: faraday,ftgmac100: Add phys mode Ninad Palsule
2025-01-18 3:51 ` Jakub Kicinski
2025-01-16 20:35 ` [PATCH v6 02/10] bindings: ipmi: Add binding for IPMB device intf Ninad Palsule
2025-01-22 15:10 ` Ninad Palsule
2025-01-22 15:32 ` Krzysztof Kozlowski
2025-01-23 22:12 ` Rob Herring (Arm) [this message]
2025-01-16 20:35 ` [PATCH v6 03/10] dt-bindings: gpio: ast2400-gpio: Add hogs parsing Ninad Palsule
2025-01-22 15:16 ` Ninad Palsule
2025-01-23 22:17 ` Rob Herring
2025-01-16 20:35 ` [PATCH v6 04/10] ARM: dts: aspeed: system1: Add IPMB device Ninad Palsule
2025-01-22 16:03 ` Eddie James
2025-01-16 20:35 ` [PATCH v6 05/10] ARM: dts: aspeed: system1: Add GPIO line name Ninad Palsule
2025-01-22 16:04 ` Eddie James
2025-01-16 20:35 ` [PATCH v6 06/10] ARM: dts: aspeed: system1: Reduce sgpio speed Ninad Palsule
2025-01-22 16:05 ` Eddie James
2025-01-16 20:35 ` [PATCH v6 07/10] ARM: dts: aspeed: system1: Update LED gpio name Ninad Palsule
2025-01-22 16:07 ` Eddie James
2025-01-16 20:35 ` [PATCH v6 08/10] ARM: dts: aspeed: system1: Remove VRs max8952 Ninad Palsule
2025-01-22 16:11 ` Eddie James
2025-01-16 20:35 ` [PATCH v6 09/10] ARM: dts: aspeed: system1: Mark GPIO line high/low Ninad Palsule
2025-01-22 16:08 ` Eddie James
2025-01-16 20:35 ` [PATCH v6 10/10] ARM: dts: aspeed: system1: Disable gpio pull down Ninad Palsule
2025-01-22 16:09 ` 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=173767032899.448455.5833909744401276024.robh@kernel.org \
--to=robh@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.ibm.com \
--cc=edumazet@google.com \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=netdev@vger.kernel.org \
--cc=ninad@linux.ibm.com \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=pabeni@redhat.com \
/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).