From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: anish kumar <yesanishhere@gmail.com>
Cc: <perex@perex.cz>, <tiwai@suse.com>, <corbet@lwn.net>,
<linux-kernel@vger.kernel.org>, <linux-sound@vger.kernel.org>,
<linux-doc@vger.kernel.org>
Subject: Re: [PATCH V3] Docs/sound: Update codec-to-codec documentation
Date: Thu, 31 Oct 2024 11:13:49 +0000 [thread overview]
Message-ID: <ZyNmbQ88HbvkaSe8@opensource.cirrus.com> (raw)
In-Reply-To: <20241028194121.41993-1-yesanishhere@gmail.com>
On Mon, Oct 28, 2024 at 12:41:21PM -0700, anish kumar wrote:
> Updated documentation to provide more details
> for codec-to-codec connection.
>
> Signed-off-by: anish kumar <yesanishhere@gmail.com>
> ---
> v3: took care of comments from Charles Keepax and
> as advised modified some details.
This still has all the DPCM bits in it.
Thanks,
Charles
next prev parent reply other threads:[~2024-10-31 11:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 19:41 [PATCH V3] Docs/sound: Update codec-to-codec documentation anish kumar
2024-10-31 11:13 ` Charles Keepax [this message]
2024-10-31 17:29 ` 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=ZyNmbQ88HbvkaSe8@opensource.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=corbet@lwn.net \
--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.