From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 92F6DC433F5 for ; Tue, 19 Oct 2021 05:58:07 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 76400610A3 for ; Tue, 19 Oct 2021 05:58:07 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233925AbhJSGAS (ORCPT ); Tue, 19 Oct 2021 02:00:18 -0400 Received: from smtp-out2.suse.de ([195.135.220.29]:34198 "EHLO smtp-out2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229742AbhJSGAS (ORCPT ); Tue, 19 Oct 2021 02:00:18 -0400 Received: from relay2.suse.de (relay2.suse.de [149.44.160.134]) by smtp-out2.suse.de (Postfix) with ESMTP id BD2421FD8A; Tue, 19 Oct 2021 05:58:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1634623084; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=jhuE+a3nW26ZUlR4nngDhL7q5YLXswWuTuaD5Bv6Wys=; b=bDcZobb44aaiE7FUwCS0gfVfKOCyOy4p5h4wElZpB0Q1llBXmhAPe6lP2KBaw7UvkXhiq7 Bl9i4lNUMgOgpeWXcadKmze+lsncVxyGVov2gLNnyRkkLFOY7FxcOREGTeBAThMwOutqAs skX8aQFpBH/4I7Zx5E56HWg1gagmTiU= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1634623084; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=jhuE+a3nW26ZUlR4nngDhL7q5YLXswWuTuaD5Bv6Wys=; b=kguE5FEMcWnMc19f6TExVk/jijQhbhwycCuXQ6J2j076QXqjTP60drtJ56jdx3sjDyp3NM q/uYIPMfvPy6mkAA== Received: from alsa1.suse.de (alsa1.suse.de [10.160.4.42]) by relay2.suse.de (Postfix) with ESMTP id B6328A3B87; Tue, 19 Oct 2021 05:58:04 +0000 (UTC) Date: Tue, 19 Oct 2021 07:58:04 +0200 Message-ID: From: Takashi Iwai To: Stephen Rothwell Cc: Linux Kernel Mailing List , Linux Next Mailing List Subject: Re: linux-next: build warnings after merge of the sound tree In-Reply-To: <20211019165402.4fa82c38@canb.auug.org.au> References: <20211019165402.4fa82c38@canb.auug.org.au> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org 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