From: Sudeep Holla <sudeep.holla@arm.com>
To: broonie@kernel.org, Cristian Marussi <cristian.marussi@arm.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
lukasz.luba@arm.com, Jonathan.Cameron@Huawei.com,
broonie@kernel.org, robh@kernel.org, satyakim@qti.qualcomm.com,
etienne.carriere@linaro.org, f.fainelli@gmail.com,
vincent.guittot@linaro.org, souvik.chakravarty@arm.com,
Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH v5 4/5] regulator: add SCMI driver
Date: Thu, 19 Nov 2020 16:13:08 +0000 [thread overview]
Message-ID: <20201119161308.xhyohop5fspb4b5l@bogus> (raw)
In-Reply-To: <20201117123415.55105-5-cristian.marussi@arm.com>
Hi Mark,
On Tue, Nov 17, 2020 at 12:34:14PM +0000, Cristian Marussi wrote:
> Add a simple regulator based on SCMI Voltage Domain Protocol.
>
I was thinking about how to merge this if and when you have reviewed it
and happy with it. Is it OK to take via ARM SoC with dependent and other
SCMI changes ? Or we can merge the SCMI part next release and the regulator
in the following, up to you.
--
Regards,
Sudeep
next prev parent reply other threads:[~2020-11-19 16:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 12:34 [PATCH v5 0/5] Add support for SCMIv3.0 Voltage Domain Protocol and SCMI-Regulator Cristian Marussi
2020-11-17 12:34 ` [PATCH v5 1/5] firmware: arm_scmi: Add Voltage Domain Support Cristian Marussi
2020-11-19 16:08 ` Sudeep Holla
2020-11-19 19:01 ` Cristian Marussi
2020-11-17 12:34 ` [PATCH v5 2/5] firmware: arm_scmi: add SCMI Voltage Domain devname Cristian Marussi
2020-11-17 12:34 ` [PATCH v5 3/5] regulator: core: add of_match_full_name boolean flag Cristian Marussi
2020-11-17 12:34 ` [PATCH v5 4/5] regulator: add SCMI driver Cristian Marussi
2020-11-19 16:13 ` Sudeep Holla [this message]
2020-11-19 16:26 ` Cristian Marussi
2020-11-19 16:39 ` Mark Brown
2020-11-19 17:24 ` Sudeep Holla
2020-11-17 12:34 ` [PATCH v5 5/5] dt-bindings: arm: add support for SCMI Regulators Cristian Marussi
2020-11-19 15:27 ` Sudeep Holla
2020-11-19 19:09 ` Cristian Marussi
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=20201119161308.xhyohop5fspb4b5l@bogus \
--to=sudeep.holla@arm.com \
--cc=Jonathan.Cameron@Huawei.com \
--cc=broonie@kernel.org \
--cc=cristian.marussi@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=etienne.carriere@linaro.org \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=robh@kernel.org \
--cc=satyakim@qti.qualcomm.com \
--cc=souvik.chakravarty@arm.com \
--cc=vincent.guittot@linaro.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