From: Eric Biggers <ebiggers@kernel.org>
To: Takashi Iwai <tiwai@suse.de>, Baojun Xu <baojun.xu@ti.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
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 crc and sound trees
Date: Sun, 19 Jan 2025 23:28:10 -0800 [thread overview]
Message-ID: <20250120072810.GA68617@sol.localdomain> (raw)
In-Reply-To: <20250120181744.6433557e@canb.auug.org.au>
On Mon, Jan 20, 2025 at 06:17:44PM +1100, Stephen Rothwell wrote:
> Probably caused by commit
>
> bb5f86ea50ff ("ALSA: hda/tas2781: Add tas2781 hda SPI driver")
>
> from the sound tree - it selects CRC32_SARWATE.
It needs to select CRC32, not CRC32_SARWATE. See 86c96e7289c5 where I already
fixed the last one. Not sure why the same bug is getting added again.
- Eric
next prev parent reply other threads:[~2025-01-20 7:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 7:17 linux-next: build failure after merge of the crc and sound trees Stephen Rothwell
2025-01-20 7:28 ` Eric Biggers [this message]
2025-01-20 7:42 ` 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=20250120072810.GA68617@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=baojun.xu@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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).