Linux-Next discussions
 help / color / mirror / Atom feed
From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Randy Dunlap <rdunlap@infradead.org>, Daniel Mack <zonque@gmail.com>
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>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	moderated for non-subscribers <alsa-devel@alsa-project.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Daniel Mack <daniel@zonque.org>,
	Haojian Zhuang <haojian.zhuang@gmail.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: linux-next: Tree for Jul 2 (sound/soc/pxa/)
Date: Mon, 02 Jul 2018 21:22:45 +0200	[thread overview]
Message-ID: <87h8lhh27u.fsf@belgarion.home> (raw)
In-Reply-To: <c12cc7c4-03d0-4b0b-d02f-7e72b8a135d4@infradead.org> (Randy Dunlap's message of "Mon, 2 Jul 2018 09:41:16 -0700")

Randy Dunlap <rdunlap@infradead.org> writes:
> [add other maintainers]
> on i386 or x86_64:
> 
> builtin:
> sound/soc/pxa/pxa-ssp.o:(.rodata+0x228): undefined reference to `pxa2xx_soc_pcm_new'
> sound/soc/pxa/pxa-ssp.o:(.rodata+0x22c): undefined reference to `pxa2xx_pcm_free_dma_buffers'
> sound/soc/pxa/pxa-ssp.o:(.rodata+0x250): undefined reference to `pxa2xx_pcm_ops'

Hi Randy,

I think the fix is already queued in Mark's tree, the commit message should be
"ASoC: pxa: select SND_PXA2XX_LIB for drivers that depend on it".

Adding Daniel as he is the original author.

Cheers.

--
Robert

  reply	other threads:[~2018-07-02 19:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-02  4:51 linux-next: Tree for Jul 2 Stephen Rothwell
2018-07-02 16:09 ` linux-next: Tree for Jul 2 (sound/soc/pxa/) Randy Dunlap
2018-07-02 16:41   ` Randy Dunlap
2018-07-02 19:22     ` Robert Jarzmik [this message]
2018-07-02 16:39 ` linux-next: Tree for Jul 2 (media/pci/meye/) Randy Dunlap

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=87h8lhh27u.fsf@belgarion.home \
    --to=robert.jarzmik@free.fr \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=daniel@zonque.org \
    --cc=haojian.zhuang@gmail.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=zonque@gmail.com \
    /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