All of lore.kernel.org
 help / color / mirror / Atom feed
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>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>
Subject: Re: linux-next: Tree for Mar 5 (sound/soc/codecs/wcd934x.o)
Date: Fri, 6 Mar 2020 13:17:52 +0100	[thread overview]
Message-ID: <CAMuHMdUs00Qtm0CMBTougPyTZxS_cN+x8QWezs_OtPFWB0B2Pw@mail.gmail.com> (raw)
In-Reply-To: <fabd49c7-d72e-a5a2-7f2c-47a8bd6c36a1@infradead.org>

Hi Randy,

On Thu, Mar 5, 2020 at 5:49 PM Randy Dunlap <rdunlap@infradead.org> wrote:
> On 3/4/20 10:55 PM, Stephen Rothwell wrote:
> > Changes since 20200304:
> >
>
> on x86_64:
>
> CONFIG_MFD_WCD934X=m
> CONFIG_SND_SOC_WCD934X=y
>
> ld: sound/soc/codecs/wcd934x.o: in function `wcd934x_trigger':
> wcd934x.c:(.text+0x754): undefined reference to `slim_stream_prepare'
> ld: wcd934x.c:(.text+0x768): undefined reference to `slim_stream_enable'
> ld: wcd934x.c:(.text+0x797): undefined reference to `slim_stream_unprepare'
> ld: wcd934x.c:(.text+0x7ab): undefined reference to `slim_stream_disable'
> ld: sound/soc/codecs/wcd934x.o: in function `wcd934x_codec_probe':
> wcd934x.c:(.text+0x4c6c): undefined reference to `of_slim_get_device'
> ld: wcd934x.c:(.text+0x4cd4): undefined reference to `slim_get_logical_addr'
> ld: wcd934x.c:(.text+0x4cfe): undefined reference to `__regmap_init_slimbus'
> ld: sound/soc/codecs/wcd934x.o: in function `wcd934x_hw_params':
> wcd934x.c:(.text+0x6027): undefined reference to `slim_stream_allocate'

This is fixed by:
https://lore.kernel.org/linux-doc/20200302062340.21453-1-masahiroy@kernel.org/

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

WARNING: multiple messages have this Message-ID (diff)
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	moderated for non-subscribers <alsa-devel@alsa-project.org>,
	Mark Brown <broonie@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Tree for Mar 5 (sound/soc/codecs/wcd934x.o)
Date: Fri, 6 Mar 2020 13:17:52 +0100	[thread overview]
Message-ID: <CAMuHMdUs00Qtm0CMBTougPyTZxS_cN+x8QWezs_OtPFWB0B2Pw@mail.gmail.com> (raw)
In-Reply-To: <fabd49c7-d72e-a5a2-7f2c-47a8bd6c36a1@infradead.org>

Hi Randy,

On Thu, Mar 5, 2020 at 5:49 PM Randy Dunlap <rdunlap@infradead.org> wrote:
> On 3/4/20 10:55 PM, Stephen Rothwell wrote:
> > Changes since 20200304:
> >
>
> on x86_64:
>
> CONFIG_MFD_WCD934X=m
> CONFIG_SND_SOC_WCD934X=y
>
> ld: sound/soc/codecs/wcd934x.o: in function `wcd934x_trigger':
> wcd934x.c:(.text+0x754): undefined reference to `slim_stream_prepare'
> ld: wcd934x.c:(.text+0x768): undefined reference to `slim_stream_enable'
> ld: wcd934x.c:(.text+0x797): undefined reference to `slim_stream_unprepare'
> ld: wcd934x.c:(.text+0x7ab): undefined reference to `slim_stream_disable'
> ld: sound/soc/codecs/wcd934x.o: in function `wcd934x_codec_probe':
> wcd934x.c:(.text+0x4c6c): undefined reference to `of_slim_get_device'
> ld: wcd934x.c:(.text+0x4cd4): undefined reference to `slim_get_logical_addr'
> ld: wcd934x.c:(.text+0x4cfe): undefined reference to `__regmap_init_slimbus'
> ld: sound/soc/codecs/wcd934x.o: in function `wcd934x_hw_params':
> wcd934x.c:(.text+0x6027): undefined reference to `slim_stream_allocate'

This is fixed by:
https://lore.kernel.org/linux-doc/20200302062340.21453-1-masahiroy@kernel.org/

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

  reply	other threads:[~2020-03-06 12:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-05  6:55 linux-next: Tree for Mar 5 Stephen Rothwell
2020-03-05 16:13 ` linux-next: Tree for Mar 5 (bpf_trace) Randy Dunlap
2020-03-05 16:18   ` Alexei Starovoitov
2020-03-05 16:22     ` KP Singh
2020-03-05 17:32       ` KP Singh
2020-03-05 17:38         ` Alexei Starovoitov
2020-03-05 22:04           ` KP Singh
2020-03-05 16:20 ` linux-next: Tree for Mar 5 (staging/media/: rockchip) Randy Dunlap
2020-03-05 16:49 ` linux-next: Tree for Mar 5 (sound/soc/codecs/wcd934x.o) Randy Dunlap
2020-03-05 16:49   ` Randy Dunlap
2020-03-06 12:17   ` Geert Uytterhoeven [this message]
2020-03-06 12:17     ` Geert Uytterhoeven

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=CAMuHMdUs00Qtm0CMBTougPyTZxS_cN+x8QWezs_OtPFWB0B2Pw@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.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 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.