devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: "Ricardo Cañuelo" <ricardo.canuelo@collabora.com>
Cc: kernel@collabora.com, groeck@chromium.org,
	dmitry.torokhov@gmail.com, bleung@chromium.org,
	dianders@chromium.org, cychiang@chromium.org,
	devicetree@vger.kernel.org, enric.balletbo@collabora.com,
	tzungbi@google.com, sjg@chromium.org
Subject: Re: [PATCH v3 3/3] mfd: google,cros-ec: add missing properties
Date: Fri, 23 Oct 2020 11:54:24 -0500	[thread overview]
Message-ID: <20201023165424.GA2858408@bogus> (raw)
In-Reply-To: <20201021114308.25485-4-ricardo.canuelo@collabora.com>

On Wed, 21 Oct 2020 13:43:08 +0200, Ricardo Cañuelo wrote:
> Add missing properties that are currently used in the examples of
> subnode bindings and in many DTs.
> 
> Also updates the example in sound/google,cros-ec-codec.yaml to comply
> with the google,cros-ec binding.
> 
> Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com>
> ---
>  .../bindings/mfd/google,cros-ec.yaml          | 42 +++++++++++++++++++
>  .../bindings/sound/google,cros-ec-codec.yaml  | 26 +++++++-----
>  2 files changed, 58 insertions(+), 10 deletions(-)
> 

Applied, thanks!

      parent reply	other threads:[~2020-10-23 16:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-21 11:43 [PATCH v3 0/3] Fix checker warnings related to cros-ec binding Ricardo Cañuelo
2020-10-21 11:43 ` [PATCH v3 1/3] dt-bindings: i2c: convert i2c-cros-ec-tunnel to json-schema Ricardo Cañuelo
2020-10-23 16:52   ` Rob Herring
2020-10-21 11:43 ` [PATCH v3 2/3] dt-bindings: input: convert cros-ec-keyb " Ricardo Cañuelo
2020-10-21 15:09   ` Enric Balletbo i Serra
2020-10-23 16:54   ` Rob Herring
2020-10-21 11:43 ` [PATCH v3 3/3] mfd: google,cros-ec: add missing properties Ricardo Cañuelo
2020-10-21 15:14   ` Enric Balletbo i Serra
2020-10-23 16:54   ` Rob Herring [this message]

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=20201023165424.GA2858408@bogus \
    --to=robh@kernel.org \
    --cc=bleung@chromium.org \
    --cc=cychiang@chromium.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=enric.balletbo@collabora.com \
    --cc=groeck@chromium.org \
    --cc=kernel@collabora.com \
    --cc=ricardo.canuelo@collabora.com \
    --cc=sjg@chromium.org \
    --cc=tzungbi@google.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).