public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Takashi Iwai <tiwai@suse.de>,
	Kriish Sharma <kriish.sharma2006@gmail.com>
Cc: Vinod Koul <vkoul@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
	Takashi Iwai <tiwai@suse.com>,
	linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	Alexey Klimov <alexey.klimov@linaro.org>
Subject: Re: [PATCH] docs: sound: describe 'chan_map' member in snd_dec_opus
Date: Sat, 27 Sep 2025 18:59:03 +0700	[thread overview]
Message-ID: <aNfRhzjqs6Z2fi-n@archie.me> (raw)
In-Reply-To: <878qi0b97l.wl-tiwai@suse.de>

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

On Sat, Sep 27, 2025 at 10:17:34AM +0200, Takashi Iwai wrote:
> On Fri, 26 Sep 2025 18:26:58 +0200,
> Kriish Sharma wrote:
> > 
> > When building kernel docs, the following warning appeared:
> > 
> >   WARNING: ./include/uapi/sound/compress_params.h:364 struct member 'chan_map' not described in 'snd_dec_opus'
> > 
> > The inline struct 'snd_dec_opus_ch_map' inside 'snd_dec_opus' was not properly documented.
> > This patch documents the 'chan_map' member and its fields (stream_count, coupled_count, channel_map), resolving the warning.
> > 
> > Signed-off-by: Kriish Sharma <kriish.sharma2006@gmail.com>
> 
> Adding Alexey to Cc, as it was added by his patch.
> 
> If any, please resubmit with a proper subject line (e.g. "ALSA:
> compress: ....") as well as the Fixes tag pointing to the affecting
> commit.

In this case, the Fixes: tag should be:

Fixes: 5d36370f3431 ("ALSA: compress: add raw opus codec define and opus decoder structs")

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

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

  reply	other threads:[~2025-09-27 11:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-26 16:26 [PATCH] docs: sound: describe 'chan_map' member in snd_dec_opus Kriish Sharma
2025-09-27  8:17 ` Takashi Iwai
2025-09-27 11:59   ` Bagas Sanjaya [this message]
     [not found]     ` <CAL4kbRMp912C+xqO4RYnGBO_VSqXJDSkNMgktd04zcUMOn_4-w@mail.gmail.com>
2025-09-27 13:03       ` Kriish Sharma
2025-09-27 13:48         ` Bagas Sanjaya
2025-09-27 11:50 ` Bagas Sanjaya

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=aNfRhzjqs6Z2fi-n@archie.me \
    --to=bagasdotme@gmail.com \
    --cc=alexey.klimov@linaro.org \
    --cc=kriish.sharma2006@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    --cc=tiwai@suse.de \
    --cc=vkoul@kernel.org \
    /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