From: Takashi Iwai <tiwai@suse.de>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Takashi Iwai <tiwai@suse.de>, Baojun Xu <baojun.xu@ti.com>,
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: Mon, 20 Jan 2025 08:42:47 +0100 [thread overview]
Message-ID: <87sepeorrc.wl-tiwai@suse.de> (raw)
In-Reply-To: <20250120072810.GA68617@sol.localdomain>
On Mon, 20 Jan 2025 08:28:10 +0100,
Eric Biggers wrote:
>
> 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.
Sorry for the overlook. That's a new driver from the past after long
development time, and obviously we overlooked this upstream change for
i2c driver.
Will queue up your suggested fix.
thanks,
Takashi
prev parent reply other threads:[~2025-01-20 7:42 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
2025-01-20 7:42 ` Takashi Iwai [this message]
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=87sepeorrc.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=baojun.xu@ti.com \
--cc=ebiggers@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).