From: Takashi Iwai <tiwai@suse.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Takashi Iwai <tiwai@suse.de>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Stefan Binding <sbinding@opensource.cirrus.com>,
Vitaly Rodionov <vitalyr@opensource.cirrus.com>
Subject: Re: linux-next: build failure after merge of the sound tree
Date: Fri, 15 Jul 2022 16:41:25 +0200 [thread overview]
Message-ID: <87fsj2v3oq.wl-tiwai@suse.de> (raw)
In-Reply-To: <20220715224443.46ce75ca@canb.auug.org.au>
On Fri, 15 Jul 2022 14:44:43 +0200,
Stephen Rothwell wrote:
>
> Hi all,
>
> After merging the sound tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> sound/pci/hda/cs35l41_hda.c: In function 'cs35l41_get_acpi_sub_string':
> sound/pci/hda/cs35l41_hda.c:693:43: error: invalid use of undefined type 'struct acpi_device'
> 693 | status = acpi_evaluate_object(adev->handle, "_SUB", NULL, &buffer);
> | ^~
>
> Caused by commit
>
> d60b05b4c780 ("ALSA: hda: cs35l41: Allow compilation test on non-ACPI configurations")
>
> along with commit
>
> eef375960210 ("ALSA: hda: cs35l41: Support reading subsystem id from ACPI")
>
> I have reverted commit d60b05b4c780 for today.
Thanks. Now I reverted the commit on for-next branch as a workaround,
too.
Takashi
next prev parent reply other threads:[~2022-07-15 14:41 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 12:44 linux-next: build failure after merge of the sound tree Stephen Rothwell
2022-07-15 14:41 ` Takashi Iwai [this message]
2022-07-15 19:09 ` Andy Shevchenko
-- strict thread matches above, loose matches on Subject: below --
2025-06-16 3:01 Stephen Rothwell
2025-06-16 5:29 ` Christophe Leroy
2025-02-12 1:09 Stephen Rothwell
2025-02-12 7:22 ` Takashi Iwai
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
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=87fsj2v3oq.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sbinding@opensource.cirrus.com \
--cc=sfr@canb.auug.org.au \
--cc=vitalyr@opensource.cirrus.com \
/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