From: Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>
To: "Chia-Wei, Wang" <chiawei_wang@aspeedtech.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
ryan_chen@aspeedtech.com, linux-aspeed@lists.ozlabs.org,
andrew@aj.id.au, openbmc@lists.ozlabs.org,
linux-kernel@vger.kernel.org, robh+dt@kernel.org, joel@jms.id.au,
jason.m.bills@linux.intel.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] peci: aspeed: Add AST2600 compatible
Date: Wed, 2 Oct 2019 11:11:28 -0700 [thread overview]
Message-ID: <70044749-785b-6ff3-7a28-fb049dcfec54@linux.intel.com> (raw)
In-Reply-To: <20191002061200.29888-1-chiawei_wang@aspeedtech.com>
Hi Chia-Wei,
On 10/1/2019 11:11 PM, Chia-Wei, Wang wrote:
> Update the Aspeed PECI driver with the AST2600 compatible string.
> A new comptabile string is needed for the extended HW feature of
> AST2600.
>
> Chia-Wei, Wang (2):
> peci: aspeed: Add AST2600 compatible string
> dt-bindings: peci: aspeed: Add AST2600 compatible
>
> Documentation/devicetree/bindings/peci/peci-aspeed.txt | 1 +
> drivers/peci/peci-aspeed.c | 1 +
> 2 files changed, 2 insertions(+)
>
PECI subsystem isn't in linux upstream yet so you should submit it into
OpenBMC dev-5.3 tree only.
Cheers,
Jae
_______________________________________________
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:[~2019-10-02 18:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 6:11 [PATCH 0/2] peci: aspeed: Add AST2600 compatible Chia-Wei, Wang
2019-10-02 6:11 ` [PATCH 1/2] peci: aspeed: Add AST2600 compatible string Chia-Wei, Wang
2019-10-02 6:12 ` [PATCH 2/2] dt-bindings: peci: aspeed: Add AST2600 compatible Chia-Wei, Wang
2019-10-15 19:01 ` Rob Herring
2019-10-02 18:11 ` Jae Hyun Yoo [this message]
2019-10-02 22:05 ` [PATCH 0/2] " Joel Stanley
2019-10-02 23:42 ` Jae Hyun Yoo
2019-10-03 2:35 ` ChiaWei Wang
2019-10-03 16:20 ` Jae Hyun Yoo
2019-10-04 1:34 ` ChiaWei 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=70044749-785b-6ff3-7a28-fb049dcfec54@linux.intel.com \
--to=jae.hyun.yoo@linux.intel.com \
--cc=andrew@aj.id.au \
--cc=chiawei_wang@aspeedtech.com \
--cc=devicetree@vger.kernel.org \
--cc=jason.m.bills@linux.intel.com \
--cc=joel@jms.id.au \
--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=openbmc@lists.ozlabs.org \
--cc=robh+dt@kernel.org \
--cc=ryan_chen@aspeedtech.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).