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 failure after merge of the sound-current tree
Date: Wed, 10 Nov 2021 10:00:03 +1100 [thread overview]
Message-ID: <20211110100003.07043ecc@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]
Hi all,
After merging the sound-current tree, today's linux-next build (x86_64
allmodconfig) failed like this:
sound/core/memalloc.c:720:32: error: 'snd_dma_sg_wc_ops' undeclared here (not in a function); did you mean 'snd_dma_sg_ops'?
720 | [SNDRV_DMA_TYPE_DEV_WC_SG] = &snd_dma_sg_wc_ops,
| ^~~~~~~~~~~~~~~~~
| snd_dma_sg_ops
sound/core/memalloc.c:651:12: error: 'snd_dma_sg_wc_mmap' defined but not used [-Werror=unused-function]
651 | static int snd_dma_sg_wc_mmap(struct snd_dma_buffer *dmab,
| ^~~~~~~~~~~~~~~~~~
sound/core/memalloc.c:641:13: error: 'snd_dma_sg_wc_free' defined but not used [-Werror=unused-function]
641 | static void snd_dma_sg_wc_free(struct snd_dma_buffer *dmab)
| ^~~~~~~~~~~~~~~~~~
sound/core/memalloc.c:628:14: error: 'snd_dma_sg_wc_alloc' defined but not used [-Werror=unused-function]
628 | static void *snd_dma_sg_wc_alloc(struct snd_dma_buffer *dmab, size_t size)
| ^~~~~~~~~~~~~~~~~~~
Caused by commit
d51f779940fb ("ALSA: memalloc: Unify x86 SG-buffer handling (take#2)")
I have used the sound-current tree from next-20211109 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-11-09 23:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 23:00 Stephen Rothwell [this message]
2021-11-10 6:20 ` linux-next: build failure after merge of the sound-current tree Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2024-03-12 21:51 Stephen Rothwell
2024-03-13 8:01 ` Takashi Iwai
2020-06-04 22:43 Stephen Rothwell
2020-06-05 2:18 ` Macpaul Lin
2020-06-05 6:39 ` 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=20211110100003.07043ecc@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=tiwai@suse.de \
/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