From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Bard Liao <bardliao@realtek.com>,
Oder Chiou <oder_chiou@realtek.com>
Subject: Re: linux-next: Tree for Nov 15 (sound/soc/codecs/rt5677)
Date: Fri, 15 Nov 2019 08:35:35 -0800 [thread overview]
Message-ID: <c505aa5d-086e-cb7d-55c0-cd092f62e82a@infradead.org> (raw)
In-Reply-To: <20191115190525.77efdf6c@canb.auug.org.au>
On 11/15/19 12:05 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20191114:
>
on i386:
when CONFIG_SPI is not set/enabled:
ld: sound/soc/codecs/rt5677.o: in function `rt5677_dsp_work':
rt5677.c:(.text+0x2cb7): undefined reference to `rt5677_spi_write'
ld: sound/soc/codecs/rt5677.o: in function `rt5677_check_hotword':
rt5677.c:(.text+0x3120): undefined reference to `rt5677_spi_hotword_detected'
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
next prev parent reply other threads:[~2019-11-15 16:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 8:05 linux-next: Tree for Nov 15 Stephen Rothwell
2019-11-15 16:02 ` linux-next: Tree for Nov 15 (objtool) Randy Dunlap
2019-11-15 16:38 ` Josh Poimboeuf
2020-01-20 15:37 ` Josh Poimboeuf
2019-11-15 16:11 ` linux-next: Tree for Nov 15 Naresh Kamboju
2019-11-15 16:17 ` linux-next: Tree for Nov 15 (drivers/md/dm-integrity) Randy Dunlap
2019-11-15 16:19 ` Randy Dunlap
2019-11-15 19:27 ` Mike Snitzer
2019-11-18 16:32 ` Alasdair G Kergon
2019-11-15 22:46 ` Stephen Rothwell
2019-11-15 23:10 ` Mike Snitzer
2019-11-15 23:32 ` Stephen Rothwell
2019-11-15 16:35 ` Randy Dunlap [this message]
2019-11-15 23:44 ` linux-next: Tree for Nov 15 (thermal: THERMAL_GOV_POWER_ALLOCATOR) Randy Dunlap
2019-12-04 16:25 ` Randy Dunlap
2019-12-05 4:27 ` Zhang Rui
2019-12-05 4:36 ` Quentin Perret
2019-12-05 5:50 ` Zhang Rui
2019-12-05 5:47 ` 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=c505aa5d-086e-cb7d-55c0-cd092f62e82a@infradead.org \
--to=rdunlap@infradead.org \
--cc=bardliao@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=oder_chiou@realtek.com \
--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
all inboxes | Powered by JetHome®