From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>,
anish kumar <yesanishhere@gmail.com>,
lgirdwood@gmail.com, broonie@kernel.org, perex@perex.cz,
tiwai@suse.com
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-sound@vger.kernel.org
Subject: Re: [PATCH V2] ALSA: machine: update documentation
Date: Sat, 9 Nov 2024 08:51:02 +0700 [thread overview]
Message-ID: <Zy7ABgpAcxrpid5Y@archie.me> (raw)
In-Reply-To: <87y11twmlx.fsf@trenco.lwn.net>
[-- Attachment #1: Type: text/plain, Size: 785 bytes --]
On Fri, Nov 08, 2024 at 12:29:14PM -0700, Jonathan Corbet wrote:
> anish kumar <yesanishhere@gmail.com> writes:
> > +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.
My htmldocs build gets:
Documentation/sound/soc/machine.rst:81: WARNING: Literal block expected; none found.
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-11-09 1:51 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
2024-11-09 1:51 ` Bagas Sanjaya [this message]
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=Zy7ABgpAcxrpid5Y@archie.me \
--to=bagasdotme@gmail.com \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox