From: Rob Herring <robh@kernel.org>
To: Quan Nguyen <quan@os.amperecomputing.com>
Cc: Corey Minyard <minyard@acm.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Brendan Higgins <brendanhiggins@google.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Joel Stanley <joel@jms.id.au>, Andrew Jeffery <andrew@aj.id.au>,
Wolfram Sang <wsa@kernel.org>,
openipmi-developer@lists.sourceforge.net,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-i2c@vger.kernel.org, openbmc@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org,
Open Source Submission <patches@amperecomputing.com>,
Phong Vo <phong@os.amperecomputing.com>,
"Thang Q . Nguyen" <thang@os.amperecomputing.com>
Subject: Re: [PATCH v8 2/3] bindings: ipmi: Add binding for SSIF BMC driver
Date: Mon, 27 Jun 2022 16:00:58 -0600 [thread overview]
Message-ID: <20220627220058.GA3036977-robh@kernel.org> (raw)
In-Reply-To: <20220615090259.1121405-3-quan@os.amperecomputing.com>
On Wed, Jun 15, 2022 at 04:02:58PM +0700, Quan Nguyen wrote:
> Add device tree binding document for the SSIF BMC driver.
>
> Signed-off-by: Quan Nguyen <quan@os.amperecomputing.com>
> ---
> v8:
> + None
>
> v7:
> + Change compatible string from "ampere,ssif-bmc" to "ssif-bmc" [Jae]
>
> v6:
> + None
>
> v5:
> + None
>
> v4:
> + Fix warning with dt_binding_check [Rob]
> + Change aspeed-ssif-bmc.yaml to ssif-bmc.yaml [Quan]
>
> v3:
> + Switched to use DT schema format [Rob]
>
> v2:
> + None
>
> .../devicetree/bindings/ipmi/ssif-bmc.yaml | 38 +++++++++++++++++++
> 1 file changed, 38 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/ipmi/ssif-bmc.yaml
Please add Acked-by/Reviewed-by tags when posting new versions. However,
there's no need to repost patches *only* to add the tags. The upstream
maintainer will do that for acks received on the version they apply.
If a tag was not added on purpose, please state why and what changed.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-27 22:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 9:02 [PATCH v8 0/3] Add SSIF BMC driver Quan Nguyen
2022-06-15 9:02 ` [PATCH v8 1/3] ipmi: ssif_bmc: " Quan Nguyen
2022-06-15 16:06 ` Randy Dunlap
2022-06-16 7:25 ` Quan Nguyen
2022-06-16 15:02 ` Randy Dunlap
2022-06-16 10:47 ` Ryan Chen
2022-06-20 7:28 ` Quan Nguyen
2022-06-16 20:04 ` kernel test robot
2022-06-16 20:47 ` Christophe JAILLET
2022-06-20 7:16 ` Quan Nguyen
2022-06-15 9:02 ` [PATCH v8 2/3] bindings: ipmi: Add binding for " Quan Nguyen
2022-06-27 22:00 ` Rob Herring [this message]
2022-06-29 8:02 ` Quan Nguyen
2022-06-15 9:02 ` [PATCH v8 3/3] i2c: aspeed: Assert NAK when slave is busy Quan Nguyen
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=20220627220058.GA3036977-robh@kernel.org \
--to=robh@kernel.org \
--cc=andrew@aj.id.au \
--cc=benh@kernel.crashing.org \
--cc=brendanhiggins@google.com \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=openbmc@lists.ozlabs.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=patches@amperecomputing.com \
--cc=phong@os.amperecomputing.com \
--cc=quan@os.amperecomputing.com \
--cc=thang@os.amperecomputing.com \
--cc=wsa@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).