From: Haiyue Wang <haiyue.wang@linux.intel.com>
To: "Chia-Wei, Wang" <chiawei_wang@aspeedtech.com>,
robh+dt@kernel.org, lee.jones@linaro.org, joel@jms.id.au,
andrew@aj.id.au, linus.walleij@linaro.org, minyard@acm.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
openbmc@lists.ozlabs.org
Cc: BMC-SW@aspeedtech.com, cyrilbur@gmail.com, rlippert@google.com
Subject: Re: [PATCH v4 3/5] ipmi: kcs: aspeed: Adapt to new LPC DTS layout
Date: Tue, 29 Dec 2020 22:53:42 +0800 [thread overview]
Message-ID: <d436cf38-7ce2-3bea-4d0e-03003e36af42@linux.intel.com> (raw)
In-Reply-To: <20201229063157.3587-4-chiawei_wang@aspeedtech.com>
On 12/29/2020 14:31, Chia-Wei, Wang wrote:
> Add check against LPC device v2 compatible string to
> ensure that the fixed device tree layout is adopted.
> The LPC register offsets are also fixed accordingly.
>
> Signed-off-by: Chia-Wei, Wang<chiawei_wang@aspeedtech.com>
> ---
> drivers/char/ipmi/kcs_bmc_aspeed.c | 27 ++++++++++++++++-----------
> 1 file changed, 16 insertions(+), 11 deletions(-)
Acked-by: Haiyue Wang <haiyue.wang@linux.intel.com>
next prev parent reply other threads:[~2020-12-29 14:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 6:31 [PATCH v4 0/5] Remove LPC register partitioning Chia-Wei, Wang
2020-12-29 6:31 ` [PATCH v4 1/5] dt-bindings: aspeed-lpc: Remove LPC partitioning Chia-Wei, Wang
2021-01-11 20:38 ` Rob Herring
2021-01-12 2:32 ` ChiaWei Wang
2020-12-29 6:31 ` [PATCH v4 2/5] ARM: dts: Remove LPC BMC and Host partitions Chia-Wei, Wang
2020-12-29 6:31 ` [PATCH v4 3/5] ipmi: kcs: aspeed: Adapt to new LPC DTS layout Chia-Wei, Wang
2020-12-29 14:53 ` Haiyue Wang [this message]
2020-12-29 6:31 ` [PATCH v4 4/5] pinctrl: aspeed-g5: Adapt to new LPC device tree layout Chia-Wei, Wang
2020-12-29 6:31 ` [PATCH v4 5/5] soc: aspeed: " Chia-Wei, Wang
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=d436cf38-7ce2-3bea-4d0e-03003e36af42@linux.intel.com \
--to=haiyue.wang@linux.intel.com \
--cc=BMC-SW@aspeedtech.com \
--cc=andrew@aj.id.au \
--cc=chiawei_wang@aspeedtech.com \
--cc=cyrilbur@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.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=openbmc@lists.ozlabs.org \
--cc=rlippert@google.com \
--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).