From: Rob Herring <robh@kernel.org>
To: Dafna Hirschfeld <dafna.hirschfeld@collabora.com>
Cc: alsa-devel@alsa-project.org, cychiang@chromium.org,
robh+dt@kernel.org, mark.rutland@arm.com,
linux-kernel@vger.kernel.org, dafna.hirschfeld@collabora.com,
helen.koike@collabora.com, ezequiel@collabora.com,
kernel@collabora.com, dafna3@gmail.com,
devicetree@vger.kernel.org, groeck@chromium.org,
enric.balletbo@collabora.com, broonie@kernel.org,
lgirdwood@gmail.com, bleung@chromium.org
Subject: Re: [PATCH] dt-bindings: Convert the binding file google,cros-ec-codec.txt to yaml format.
Date: Wed, 5 Feb 2020 17:02:13 +0000 [thread overview]
Message-ID: <20200205170213.GA15498@bogus> (raw)
In-Reply-To: <20200127091806.11403-1-dafna.hirschfeld@collabora.com>
On Mon, 27 Jan 2020 10:18:06 +0100, Dafna Hirschfeld wrote:
> This was tested and verified with:
> make dt_binding_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/sound/google,cros-ec-codec.yaml
>
> Signed-off-by: Dafna Hirschfeld <dafna.hirschfeld@collabora.com>
> ---
> .../bindings/sound/google,cros-ec-codec.txt | 44 -------------
> .../bindings/sound/google,cros-ec-codec.yaml | 62 +++++++++++++++++++
> 2 files changed, 62 insertions(+), 44 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/sound/google,cros-ec-codec.txt
> create mode 100644 Documentation/devicetree/bindings/sound/google,cros-ec-codec.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2020-02-05 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 9:18 [PATCH] dt-bindings: Convert the binding file google,cros-ec-codec.txt to yaml format Dafna Hirschfeld
2020-02-05 17:02 ` Rob Herring [this message]
2020-02-12 12:15 ` Mark Brown
2020-02-12 23:57 ` Applied "dt-bindings: Convert the binding file google, cros-ec-codec.txt to yaml format." to the asoc tree Mark Brown
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=20200205170213.GA15498@bogus \
--to=robh@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bleung@chromium.org \
--cc=broonie@kernel.org \
--cc=cychiang@chromium.org \
--cc=dafna.hirschfeld@collabora.com \
--cc=dafna3@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=enric.balletbo@collabora.com \
--cc=ezequiel@collabora.com \
--cc=groeck@chromium.org \
--cc=helen.koike@collabora.com \
--cc=kernel@collabora.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.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).