From: Randy Dunlap <rdunlap@infradead.org>
To: Manuel Ebner <manuelebnerli@mailbox.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>, Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>
Cc: linux-sound@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] ASoC: doc: Fix bracket
Date: Sun, 22 Nov 2026 08:45:12 -0800 [thread overview]
Message-ID: <326066b5-6198-402d-bd5f-e1dfb02b305e@infradead.org> (raw)
In-Reply-To: <20261122090640.1475222-2-manuelebnerli@mailbox.org>
On 11/22/26 1:06 AM, Manuel Ebner wrote:
> Add missng '};'.
>
> Signed-off-by: Manuel Ebner <manuelebnerli@mailbox.org>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> [v4]
> Instead of remove {, add };
>
> [v3]
> https://lore.kernel.org/all/20260916113524.304863-2-manuelebnerli@mailbox.org/
> - removed the change of the placeholder
>
> [v2]
> https://lore.kernel.org/all/20260904120737.758809-2-manuelebnerli@mailbox.org/
> - rearrange lines in diff
> - fix commit message
>
> [v1]
> https://lore.kernel.org/all/20260902150510.706055-2-manuelebnerli@mailbox.org/
> ---
> ---
> Documentation/sound/soc/dpcm.rst | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/sound/soc/dpcm.rst b/Documentation/sound/soc/dpcm.rst
> index 7b6aeab3c2..3b145e8ba1 100644
> --- a/Documentation/sound/soc/dpcm.rst
> +++ b/Documentation/sound/soc/dpcm.rst
> @@ -370,6 +370,7 @@ The machine driver sets some additional parameters to the DAI link i.e.
> .num_c2c_params = 1,
> }
> < ... more DAI links here ... >
> + };
>
> These parameters are used to configure the DAI hw_params() when DAPM detects a
> valid path and then calls the PCM operations to start the link. DAPM will also
--
~Randy
prev parent reply other threads:[~2026-11-22 16:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-22 9:06 Manuel Ebner
2026-11-22 16:45 ` Randy Dunlap [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=326066b5-6198-402d-bd5f-e1dfb02b305e@infradead.org \
--to=rdunlap@infradead.org \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=lgirdwood@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=manuelebnerli@mailbox.org \
--cc=perex@perex.cz \
--cc=skhan@linuxfoundation.org \
--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
all inboxes | Powered by JetHome®