From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Takashi Iwai <tiwai@suse.de>
Cc: Johan Carlsson <johan.carlsson@teenage.engineering>,
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, 13 Mar 2024 08:51:36 +1100 [thread overview]
Message-ID: <20240313085136.056eaf24@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 741 bytes --]
Hi all,
After merging the sound-current tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
sound/usb/stream.c: In function 'convert_chmap':
sound/usb/stream.c:306:34: error: 'chmaps' undeclared (first use in this function); did you mean 'chmap'?
306 | if (c == chmaps->channels)
| ^~~~~~
| chmap
sound/usb/stream.c:306:34: note: each undeclared identifier is reported only once for each function it appears in
Caused by commit
a94566ace3ca ("ALSA: usb-audio: Stop parsing channels bits when all channels are found.")
I have reverted that commit for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-03-12 21:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 21:51 Stephen Rothwell [this message]
2024-03-13 8:01 ` linux-next: build failure after merge of the sound-current tree Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2021-11-09 23:00 Stephen Rothwell
2021-11-10 6:20 ` 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=20240313085136.056eaf24@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=johan.carlsson@teenage.engineering \
--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;
as well as URLs for NNTP newsgroup(s).