devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Kiseok Jo <kiseok.jo@irondevice.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
	Takashi Iwai <tiwai@suse.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	alsa-devel@alsa-project.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/3] ASoC: dt-bindings: irondevice,sma1303: Rework binding and add missing properties
Date: Fri, 3 Feb 2023 16:01:43 -0600	[thread overview]
Message-ID: <20230203220143.GA947805-robh@kernel.org> (raw)
In-Reply-To: <20230203094239.25700-1-kiseok.jo@irondevice.com>

On Fri, Feb 03, 2023 at 09:42:37AM +0000, Kiseok Jo wrote:
> Fix according to the writing-schema.rst file and tested.
> Add the missing property as compatible, reg, sys-clk-id.
> 
> Signed-off-by: Kiseok Jo <kiseok.jo@irondevice.com>
> ---
>  .../bindings/sound/irondevice,sma1303.yaml    | 35 +++++++++++++++++--
>  1 file changed, 32 insertions(+), 3 deletions(-)

What's the output of 'make dt_binding_check'? Asking since linux-next 
has been broken in different ways with this schema.

Rob

  parent reply	other threads:[~2023-02-03 22:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-03  9:42 [PATCH 1/3] ASoC: dt-bindings: irondevice,sma1303: Rework binding and add missing properties Kiseok Jo
2023-02-03  9:42 ` [PATCH 2/3] ASoC: SMA1303: Remove the I2C Retry property in devicetree Kiseok Jo
2023-02-03  9:42 ` [PATCH 3/3] ASoC: SMA1303: Convert the TDM slot properties in devicetree to mixer Kiseok Jo
2023-02-03 13:37 ` [PATCH 1/3] ASoC: dt-bindings: irondevice,sma1303: Rework binding and add missing properties Mark Brown
2023-02-04  1:20   ` Ki-Seok Jo
2023-02-03 22:01 ` Rob Herring [this message]
2023-02-04  1:17   ` Ki-Seok Jo

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=20230203220143.GA947805-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kiseok.jo@irondevice.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.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).