From: "Andrew Jeffery" <andrew@aj.id.au>
To: openipmi-developer@lists.sourceforge.net
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
"Corey Minyard" <minyard@acm.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, linux-aspeed@lists.ozlabs.org,
"Rob Herring" <robh+dt@kernel.org>,
"Haiyue Wang" <haiyue.wang@linux.intel.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/3] ipmi: kcs-bmc: Rework bindings to clean up DT warnings
Date: Fri, 03 Apr 2020 14:20:21 +1030 [thread overview]
Message-ID: <7734002a-181e-4baf-b9a3-af66894acc16@www.fastmail.com> (raw)
In-Reply-To: <cover.fe20dfec1a7c91771c6bb574814ffb4bb49e2136.1576462051.git-series.andrew@aj.id.au>
On Mon, 16 Dec 2019, at 12:57, Andrew Jeffery wrote:
> Hello,
>
> This is a short series reworking the devicetree binding and driver for the
> ASPEED BMC KCS devices. With the number of supported ASPEED BMC devicetrees the
> changes enable removal of more than 100 lines of warning output from dtc.
>
> v1 can be found here:
>
> https://lore.kernel.org/lkml/cover.5630f63168ad5cddf02e9796106f8e086c196907.1575376664.git-series.andrew@aj.id.au/
>
> v2 cleans up the commit message of 2/3 and changes the name of the property
> governing the LPC IO address for the KCS devices.
Ping?
next prev parent reply other threads:[~2020-04-03 3:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 2:27 [PATCH v2 0/3] ipmi: kcs-bmc: Rework bindings to clean up DT warnings Andrew Jeffery
2019-12-16 2:27 ` [PATCH v2 1/3] dt-bindings: ipmi: aspeed: Introduce a v2 binding for KCS Andrew Jeffery
2019-12-20 0:01 ` Rob Herring
2019-12-16 2:27 ` [PATCH v2 2/3] ipmi: kcs: Finish configuring ASPEED KCS device before enable Andrew Jeffery
2019-12-16 2:27 ` [PATCH v2 3/3] ipmi: kcs: aspeed: Implement v2 bindings Andrew Jeffery
2020-04-03 3:50 ` Andrew Jeffery [this message]
2020-04-03 13:08 ` [PATCH v2 0/3] ipmi: kcs-bmc: Rework bindings to clean up DT warnings Corey Minyard
2020-04-05 7:00 ` 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=7734002a-181e-4baf-b9a3-af66894acc16@www.fastmail.com \
--to=andrew@aj.id.au \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=haiyue.wang@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=minyard@acm.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=robh+dt@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).