All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: anish kumar <yesanishhere@gmail.com>
Cc: lgirdwood@gmail.com, broonie@kernel.org, perex@perex.cz,
	tiwai@suse.com, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-sound@vger.kernel.org
Subject: Re: [PATCH V2] ALSA: machine: update documentation
Date: Fri, 08 Nov 2024 12:53:47 -0700	[thread overview]
Message-ID: <87ldxtwlh0.fsf@trenco.lwn.net> (raw)
In-Reply-To: <CABCoZhCpMVwA5qzUL4NcSkhuW3+FnD9pH5Grhic3AWrrqX3g2w@mail.gmail.com>

[I suspect that your HTML email will keep your response off the list -
don't do that.]

anish kumar <yesanishhere@gmail.com> writes:

> On Fri, Nov 8, 2024 at 11:29 AM Jonathan Corbet <corbet@lwn.net> wrote:
>
>  anish kumar <yesanishhere@gmail.com> writes:
>  > +In the above struct, dai’s are registered using names but you can pass
>  > +either dai name or device tree node but not both. Also, names used here
>  > +for cpu/codec/platform dais should be globally unique.
>  > +
>  > +Additionaly below example macro can be used to register cpu, codec and
>  > +platform dai::
>  > +
>  > +SND_SOC_DAILINK_DEFS(wm2200_cpu_dsp,
>  > +     DAILINK_COMP_ARRAY(COMP_CPU("samsung-i2s.0")),
>  > +     DAILINK_COMP_ARRAY(COMP_CODEC("spi0.0", "wm0010-sdi1")),
>  > +     DAILINK_COMP_ARRAY(COMP_PLATFORM("samsung-i2s.0")));
>  > +
>
>  This will not give you the literal block you were hoping for.  Please
>  actually build the docs after making changes and look at the results.
>
> I was not hoping for literally code block but rather just a tab. I just pasted Bagas comment as I
> thought it is better way to say that about the change. 

The "::" you added above introduces a literal block.  Yes, that is what
you were hoping for.

jon

  parent reply	other threads:[~2024-11-08 19:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-08 19:24 [PATCH V2] ALSA: machine: update documentation anish kumar
2024-11-08 19:29 ` Jonathan Corbet
     [not found]   ` <CABCoZhCpMVwA5qzUL4NcSkhuW3+FnD9pH5Grhic3AWrrqX3g2w@mail.gmail.com>
2024-11-08 19:53     ` Jonathan Corbet [this message]
2024-11-09  1:51   ` Bagas Sanjaya
2024-11-09  3:33 ` Bagas Sanjaya
2024-11-09 19:18   ` anish kumar

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=87ldxtwlh0.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    --cc=yesanishhere@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.