public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Takashi Iwai <tiwai@suse•de>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build warnings after merge of the sound tree
Date: Tue, 19 Oct 2021 07:58:04 +0200	[thread overview]
Message-ID: <s5h8ryp4kur.wl-tiwai@suse.de> (raw)
In-Reply-To: <20211019165402.4fa82c38@canb.auug.org.au>

On Tue, 19 Oct 2021 07:54:02 +0200,
Stephen Rothwell wrote:
> 
> 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")

Thanks, I will fix this typo.

> 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.

Gah this was a leftover after some rebase.  Will fix up altogether.


thanks,

Takashi

next prev parent reply	other threads:[~2021-10-19  5:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-19  5:54 linux-next: build warnings after merge of the sound tree Stephen Rothwell
2021-10-19  5:58 ` Takashi Iwai [this message]
  -- 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=s5h8ryp4kur.wl-tiwai@suse.de \
    --to=tiwai@suse$(echo .)de \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox