linux-kernel - Re: [PATCH 10/12] ASoC: doc: dapm: improve section "Codec/DSP Widget Interconnections"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Wed, 17 Apr 2024 07:08:19 +0200
From: Luca Ceresoli <luca.ceresoli@...tlin.com>
To: Bagas Sanjaya <bagasdotme@...il.com>
Cc: Liam Girdwood <lgirdwood@...il.com>, Mark Brown <broonie@...nel.org>,
 Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>, Jonathan
 Corbet <corbet@....net>, Alexandre Belloni <alexandre.belloni@...tlin.com>,
 Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
 linux-sound@...r.kernel.org, linux-doc@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH 10/12] ASoC: doc: dapm: improve section "Codec/DSP
 Widget Interconnections"

Hello Bagas,

thanks for reviewing!

On Wed, 17 Apr 2024 11:33:12 +0700
Bagas Sanjaya <bagasdotme@...il.com> wrote:

> On Tue, Apr 16, 2024 at 07:56:16AM +0200, Luca Ceresoli wrote:
> > -Each input in this example has a kcontrol associated with it (defined in example
> > -above) and is connected to the output mixer via its kcontrol name. We can now
> > -connect the destination widget (wrt audio signal) with its source widgets.
> > -::
> > +Each input in this example has a kcontrol associated with it (defined in
> > +the example above) and is connected to the output mixer via its kcontrol
> > +name. We can now connect the destination widget (wrt audio signal) with its
> > +source widgets.  ::
> > <snipped>...
> > -Interconnections are created with a call to:
> > -::
> > +Interconnections are created with a call to::
> >    
> 
> Not strictly related to this patch, but for consistency, I'd like
> to write remaining literal block markers at the end of previous
> paragraph:

Makes sense, sure. I can add a patch doing this in v2, or send a
separate patch after this series.

Luca

-- 
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com