From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Mark Brown <broonie@kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-sound@vger.kernel.org, patches@opensource.cirrus.com,
Maciej Strozek <mstrozek@opensource.cirrus.com>
Subject: Re: linux-next: Tree for Jul 30 (sound/soc/sdca/)
Date: Fri, 31 Jul 2026 09:32:02 +0100 [thread overview]
Message-ID: <amxdgg7mKgy8/uwg@opensource.cirrus.com> (raw)
In-Reply-To: <ae2d6aa5-1093-4ec1-ab29-ac9af791fb5d@infradead.org>
On Thu, Jul 30, 2026 at 02:40:14PM -0700, Randy Dunlap wrote:
> On 7/30/26 8:02 AM, Mark Brown wrote:
> > Hi all,
> >
> > Changes since 20260729:
> >
>
> When # CONFIG_SND_SOC_SDCA_FDL is not set:
>
> ../sound/soc/sdca/sdca_interrupts.c: In function ‘sdca_irq_populate_early’:
> ../sound/soc/sdca/sdca_interrupts.c:471:56: error: ‘sdca_fdl_free_state’ undeclared (first use in this function); did you mean ‘sdca_jack_free_state’?
> 471 | interrupt->free_priv = sdca_fdl_free_state;
> | ^~~~~~~~~~~~~~~~~~~
> | sdca_jack_free_state
Yeah apologies about that, all my bad. A fix is available here:
https://lore.kernel.org/linux-sound/20260730130602.3747053-1-ckeepax@opensource.cirrus.com/T/#u
Thanks,
Charles
next prev parent reply other threads:[~2026-07-31 8:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 15:02 linux-next: Tree for Jul 30 Mark Brown
2026-07-30 21:40 ` linux-next: Tree for Jul 30 (sound/soc/sdca/) Randy Dunlap
2026-07-31 8:32 ` Charles Keepax [this message]
2026-07-30 22:11 ` linux-next: Tree for Jul 30 (usb/dwc3/) Randy Dunlap
2026-07-30 22:15 ` linux-next: Tree for Jul 30 (objtool) Randy Dunlap
2026-07-30 23:06 ` linux-next: Tree for Jul 30 (pci/controller/cadence/) Randy Dunlap
2026-07-31 0:27 ` Bjorn Helgaas
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=amxdgg7mKgy8/uwg@opensource.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mstrozek@opensource.cirrus.com \
--cc=patches@opensource.cirrus.com \
--cc=rdunlap@infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.