public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Takashi Iwai <tiwai@suse•de>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build warnings after merge of the sound tree
Date: Tue, 19 Oct 2021 16:54:02 +1100	[thread overview]
Message-ID: <20211019165402.4fa82c38@canb.auug.org.au> (raw)

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

Hi all,

After merging the sound tree, today's linux-next build (htmldocs)
produced these warnings:

sound/core/memalloc.c:203: warning: Function parameter or member 'mode' not described in 'snd_dma_buffer_sync'
sound/core/memalloc.c:203: warning: Excess function parameter 'mod' description in 'snd_dma_buffer_sync'

Introduced by commit

  a25684a95646 ("ALSA: memalloc: Support for non-contiguous page allocation")

Also, the declaration of this function in include/ound/memalloc.h looks
incorrect as it has different declarations depending on CONFIG_HAS_DMA, but
then another one afterwards.  I expect this will cause errors if
CONFIG_HAS_DMA is not set.
-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2021-10-19  5:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-19  5:54 Stephen Rothwell [this message]
2021-10-19  5:58 ` linux-next: build warnings after merge of the sound tree Takashi Iwai
  -- strict thread matches above, loose matches on Subject: below --
2024-10-28  8:32 Stephen Rothwell
2024-10-28  8:37 Stephen Rothwell
2024-11-13  6:31 ` Stephen Rothwell
2024-11-13  7:23   ` Takashi Iwai

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=20211019165402.4fa82c38@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=tiwai@suse$(echo .)de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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