devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Jerome Brunet <jbrunet@baylibre.com>,
	Mark Brown <broonie@kernel.org>,
	alsa-devel@alsa-project.org, devicetree@vger.kernel.org
Cc: linux-amlogic@lists.infradead.org,
	Kevin Hilman <khilman@baylibre.com>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 7/7] ASoC: dt-bindings: meson: convert axg sound card control to schema
Date: Tue, 7 Feb 2023 13:30:25 +0100	[thread overview]
Message-ID: <6804adf4-2fba-e4f9-36ef-a6b8bacae76d@linaro.org> (raw)
In-Reply-To: <1jbkm53jvg.fsf@starbuckisacylon.baylibre.com>

On 07/02/2023 10:25, Jerome Brunet wrote:
> 
> On Mon 06 Feb 2023 at 20:21, Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote:
> 
>>> +
>>> +  audio-routing:
>>> +    $ref: /schemas/types.yaml#/definitions/non-unique-string-array
>>> +    description: |
>>
>> You still have everywhere | which should be removed. Here and in almost
>> every other description when no special formatting is needed.
> 
> I'm sorry if I misunderstood your comment. I thought the problem was
> with the '-' of '|-', which I removed here.
> 
> Should I use '>' for the YAML multiline format instead ?

I asked to remove "|-". Don't add any other character - why do you need
it? Multiline descriptions don't need block scalar headers unless you
want to preserve some format.

Best regards,
Krzysztof


  reply	other threads:[~2023-02-07 12:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-06 15:34 [PATCH v2 0/7] ASoC: dt-bindings: meson: covert axg audio to schema Jerome Brunet
2023-02-06 15:34 ` [PATCH v2 1/7] ASoC: dt-bindings: meson: convert axg tdm interface " Jerome Brunet
2023-02-06 19:10   ` Krzysztof Kozlowski
2023-02-06 15:34 ` [PATCH v2 2/7] ASoC: dt-bindings: meson: convert axg tdm formatters " Jerome Brunet
2023-02-06 19:12   ` Krzysztof Kozlowski
2023-02-06 19:59   ` Rob Herring
2023-02-07  9:29     ` Jerome Brunet
2023-02-07 13:50       ` Rob Herring
2023-02-06 15:34 ` [PATCH v2 3/7] ASoC: dt-bindings: meson: convert axg pdm " Jerome Brunet
2023-02-06 19:13   ` Krzysztof Kozlowski
2023-02-06 15:34 ` [PATCH v2 4/7] ASoC: dt-bindings: meson: convert axg fifo " Jerome Brunet
2023-02-06 19:14   ` Krzysztof Kozlowski
2023-02-06 15:34 ` [PATCH v2 5/7] ASoC: dt-bindings: meson: convert axg spdif input " Jerome Brunet
2023-02-06 19:15   ` Krzysztof Kozlowski
2023-02-06 15:34 ` [PATCH v2 6/7] ASoC: dt-bindings: meson: convert axg spdif output " Jerome Brunet
2023-02-06 19:16   ` Krzysztof Kozlowski
2023-02-06 15:34 ` [PATCH v2 7/7] ASoC: dt-bindings: meson: convert axg sound card control " Jerome Brunet
2023-02-06 19:21   ` Krzysztof Kozlowski
2023-02-07  9:25     ` Jerome Brunet
2023-02-07 12:30       ` Krzysztof Kozlowski [this message]
2023-02-07 15:06 ` (subset) [PATCH v2 0/7] ASoC: dt-bindings: meson: covert axg audio " 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=6804adf4-2fba-e4f9-36ef-a6b8bacae76d@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jbrunet@baylibre.com \
    --cc=khilman@baylibre.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neil.armstrong@linaro.org \
    --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).