From: Mark Brown <broonie@kernel.org>
To: Prashant Malani <pmalani@chromium.org>
Cc: linux-kernel@vger.kernel.org, bleung@chromium.org,
Stephen Boyd <swboyd@chromium.org>,
"open list:CHROME HARDWARE PLATFORM SUPPORT"
<chrome-platform@lists.linux.dev>,
Daisuke Nojiri <dnojiri@chromium.org>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Guenter Roeck <groeck@chromium.org>,
Lee Jones <lee.jones@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Tzung-Bi Shih <tzungbi@kernel.org>
Subject: Re: [PATCH 1/3] regulator: cros-ec: Use common cros_ec_command()
Date: Tue, 7 Jun 2022 16:31:53 +0100 [thread overview]
Message-ID: <Yp9vadmTaNw3YCk4@sirena.org.uk> (raw)
In-Reply-To: <20220606201825.763788-2-pmalani@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 223 bytes --]
On Mon, Jun 06, 2022 at 08:18:01PM +0000, Prashant Malani wrote:
> Reduce code duplication by using the common cros_ec_command() function
> instead of the locally defined variant.
Acked-by: Mark Brown <broonie@kernel.org>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-06-07 15:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 20:17 [PATCH 0/3] platform/chrome: cros_ec_command() improvements Prashant Malani
2022-06-06 20:18 ` [PATCH 1/3] regulator: cros-ec: Use common cros_ec_command() Prashant Malani
2022-06-06 23:31 ` Stephen Boyd
2022-06-07 14:37 ` Guenter Roeck
2022-06-07 15:31 ` Mark Brown [this message]
2022-06-06 20:18 ` [PATCH 2/3] platform/chrome: cros_ec_proto: Rename cros_ec_command function Prashant Malani
2022-06-06 23:32 ` Stephen Boyd
2022-06-07 14:38 ` Guenter Roeck
2022-06-08 7:44 ` Lee Jones
2022-06-06 20:18 ` [PATCH 3/3] platform/chrome: cros_ec_proto: Update size arg types Prashant Malani
2022-06-06 23:34 ` Stephen Boyd
2022-06-07 14:41 ` Guenter Roeck
2022-06-08 8:20 ` [PATCH 0/3] platform/chrome: cros_ec_command() improvements patchwork-bot+chrome-platform
2022-06-10 2:30 ` patchwork-bot+chrome-platform
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=Yp9vadmTaNw3YCk4@sirena.org.uk \
--to=broonie@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=dnojiri@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmalani@chromium.org \
--cc=swboyd@chromium.org \
--cc=tzungbi@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
all inboxes | Powered by JetHome®