From: Takashi Iwai <tiwai@suse.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Takashi Iwai <tiwai@suse.de>,
Jack Livingood <jacklivingood@comcast.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the sound tree
Date: Wed, 12 Feb 2025 08:22:24 +0100 [thread overview]
Message-ID: <87ikpfmxu7.wl-tiwai@suse.de> (raw)
In-Reply-To: <20250212120927.40a4d24e@canb.auug.org.au>
On Wed, 12 Feb 2025 02:09:27 +0100,
Stephen Rothwell wrote:
>
> Hi all,
>
> After merging the sound tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> sound/firewire/isight.c: In function 'isight_probe':
> sound/firewire/isight.c:647:9: error: implicit declaration of function 'strspy'; did you mean 'strspn'? [-Wimplicit-function-declaration]
> 647 | strspy(card->mixername, "iSight");
> | ^~~~~~
> | strspn
>
> Caused by commit
>
> 2a91231a78a7 ("ALSA: firewire: isight: changed strcpy to strscpy")
>
> I have used the sound tree from next-20250210 for today.
Doh, I dropped the patch again. Somehow my test bench didn't run well
yesterday. Sorry for inconvenience!
Takashi
next prev parent reply other threads:[~2025-02-12 7:22 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 1:09 linux-next: build failure after merge of the sound tree Stephen Rothwell
2025-02-12 7:22 ` Takashi Iwai [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-16 3:01 Stephen Rothwell
2025-06-16 5:29 ` Christophe Leroy
2025-01-20 3:56 Stephen Rothwell
2025-01-20 7:42 ` Takashi Iwai
2024-10-11 2:10 Stephen Rothwell
2024-10-11 7:22 ` Takashi Iwai
2024-08-09 1:22 Stephen Rothwell
2024-08-09 7:43 ` Takashi Iwai
2023-08-18 3:12 Stephen Rothwell
2023-08-18 11:47 ` Takashi Iwai
2023-05-24 3:54 Stephen Rothwell
2023-05-24 7:14 ` Takashi Iwai
2022-07-15 12:44 Stephen Rothwell
2022-07-15 14:41 ` Takashi Iwai
2022-07-15 19:09 ` Andy Shevchenko
2021-10-18 0:38 Stephen Rothwell
2021-10-18 6:35 ` Takashi Iwai
2020-07-17 3:01 Stephen Rothwell
2020-07-17 5:33 ` Christoph Hellwig
2020-07-17 6:34 ` Takashi Iwai
2020-07-17 6:50 ` Christoph Hellwig
2020-07-17 6:54 ` Takashi Iwai
2019-08-09 2:54 Stephen Rothwell
2019-08-09 5:55 ` Takashi Iwai
2017-05-17 1:29 Stephen Rothwell
2017-05-17 5:30 ` Takashi Iwai
2011-09-23 2:49 Stephen Rothwell
2011-09-23 5:21 ` Takashi Iwai
2011-05-19 1:15 Stephen Rothwell
2010-09-23 2:44 Stephen Rothwell
2010-09-23 6:04 ` Takashi Iwai
2010-09-23 8:39 ` Mark Brown
2010-06-24 3:03 Stephen Rothwell
2010-06-24 6:11 ` Takashi Iwai
2010-06-28 16:33 ` Daniel Mack
2010-06-01 2:30 Stephen Rothwell
2010-06-01 5:47 ` Takashi Iwai
2010-04-07 3:39 Stephen Rothwell
2010-04-07 6:06 ` Takashi Iwai
2010-04-07 7:16 ` Stephen Rothwell
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=87ikpfmxu7.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=jacklivingood@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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