Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Manuel Ebner <manuelebnerli@mailbox.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	linux-sound@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ASoC: doc: Fix bracket and wording
Date: Fri, 4 Sep 2026 16:56:41 +0100	[thread overview]
Message-ID: <aprqOQm357605zoD@sirena.co.uk> (raw)
In-Reply-To: <20260904120737.758809-2-manuelebnerli@mailbox.org>

[-- Attachment #1: Type: text/plain, Size: 730 bytes --]

On Fri, Sep 04, 2026 at 02:07:37PM +0200, Manuel Ebner wrote:
> Change wording to make sense.
> 'above' -> 'here' in placeholder which already is above the code block.

> I guess the line is to show that there are more DAI links _above_ the code
> block. But it's already above, thus change 'above' -> 'here'
> Let me know if I misunderstood.

>    static struct snd_soc_dai_link dais[] = {
> -	< ... more DAI links above ... >
> -	{
> +        < ... more DAI links here ... >
>  		.name = "MODEM",

You've moved the bit saying more links into the definition of the link
element that's show where you obviously can't have more links since it's
a single element in the array.  Again, I'm confused what you think the
issue is here.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2026-09-04 15:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04 12:07 [PATCH v2] ASoC: doc: Fix bracket and wording Manuel Ebner
2026-09-04 15:56 ` Mark Brown [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=aprqOQm357605zoD@sirena.co.uk \
    --to=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