From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
moderated for non-subscribers <alsa-devel@alsa-project.org>,
Takashi Iwai <tiwai@suse.de>
Subject: Re: linux-next: Tree for Feb 13 (sound/soc/codecs/snd-soc-ab8500-codec)
Date: Thu, 13 Feb 2020 20:31:50 +0100 [thread overview]
Message-ID: <CAMuHMdVLbVsgTC9R6qk=TOGKwmXpg+attNq=SYhR5y807L+DAA@mail.gmail.com> (raw)
In-Reply-To: <d0d9a245-f336-1334-90a8-631faf95d071@infradead.org>
Hi Randy,
On Thu, Feb 13, 2020 at 6:41 PM Randy Dunlap <rdunlap@infradead.org> wrote:
> On 2/13/20 9:06 AM, Randy Dunlap wrote:
> > On 2/12/20 7:52 PM, Stephen Rothwell wrote:
> >> Changes since 20200212:
>
> > on x86_64:
> >
> > # CONFIG_ABX500_CORE is not set [this is in MFD]
> >
> > ERROR: "abx500_set_register_interruptible" [sound/soc/codecs/snd-soc-ab8500-codec.ko] undefined!
> > ERROR: "abx500_get_register_interruptible" [sound/soc/codecs/snd-soc-ab8500-codec.ko] undefined!
Yeah, commit d8dd3f92a6ba11f9 ("ASoC: Fix SND_SOC_ALL_CODECS imply misc
fallout") is in sound-asoc/for-next, but didn't make it in next-20200213.
I expect this to be fixed tomorrow.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2020-02-13 19:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 3:52 linux-next: Tree for Feb 13 Stephen Rothwell
2020-02-13 7:45 ` linux-next: Tree for Feb 13 (kernel/torture.c:) Randy Dunlap
2020-02-13 10:33 ` Paul E. McKenney
2020-02-13 17:06 ` linux-next: Tree for Feb 13 (sound/soc/codecs/snd-soc-ab8500-codec) Randy Dunlap
2020-02-13 17:41 ` Randy Dunlap
2020-02-13 19:31 ` Geert Uytterhoeven [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='CAMuHMdVLbVsgTC9R6qk=TOGKwmXpg+attNq=SYhR5y807L+DAA@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.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).