From: Takashi Iwai <tiwai@suse.de>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-sound@vger.kernel.org,
Takashi Sakamoto <o-takashi@sakamocchi.jp>,
Takashi Iwai <tiwai@suse.de>,
Clemens Ladisch <clemens@ladisch.de>,
Jaroslav Kysela <perex@perex.cz>
Subject: Re: [PATCH] sound: amdtp-stream: fix enum kernel-doc warnings
Date: Tue, 14 Oct 2025 15:47:21 +0200 [thread overview]
Message-ID: <87ikgh7fyu.wl-tiwai@suse.de> (raw)
In-Reply-To: <20251014030552.760648-1-rdunlap@infradead.org>
On Tue, 14 Oct 2025 05:05:52 +0200,
Randy Dunlap wrote:
>
> Fix spelling of CIP_NO_HEADER to prevent a kernel-doc warning.
>
> Warning: amdtp-stream.h:57 Enum value 'CIP_NO_HEADER' not described in enum 'cip_flags'
> Warning: amdtp-stream.h:57 Excess enum value '%CIP_NO_HEADERS' description in 'cip_flags'
>
> Fixes: 3b196c394dd9f ("ALSA: firewire-lib: add no-header packet processing")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Applied now (with the correction of subject prefix).
thanks,
Takashi
prev parent reply other threads:[~2025-10-14 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 3:05 [PATCH] sound: amdtp-stream: fix enum kernel-doc warnings Randy Dunlap
2025-10-14 13:09 ` Takashi Sakamoto
2025-10-14 13:47 ` Takashi Iwai [this message]
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=87ikgh7fyu.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=clemens@ladisch.de \
--cc=linux-sound@vger.kernel.org \
--cc=o-takashi@sakamocchi.jp \
--cc=perex@perex.cz \
--cc=rdunlap@infradead.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