linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
	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>,
	moderated for non-subscribers <alsa-devel@alsa-project.org>
Subject: Re: linux-next: Tree for Jan 29 (SLIMbus & SND_SOC_WCD9335)
Date: Tue, 29 Jan 2019 09:00:21 -0800	[thread overview]
Message-ID: <7f4aa68d-d9ee-ec08-8593-a975a999e5e2@infradead.org> (raw)
In-Reply-To: <a849e598-da5b-bfc2-cd41-dab94fa79c87@linaro.org>

On 1/29/19 8:57 AM, Srinivas Kandagatla wrote:
> 
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/commit/?h=for-5.1&id=a8233b6c1972e1959cf84a021aeb61ddcd23cc26
> 
> This should fix the issue! It should be in next today!

Looks good.  Thanks.

> Thanks,
> srini
> 
> 
> On 29/01/2019 16:50, Randy Dunlap wrote:
>> On 1/28/19 10:11 PM, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20190125:
>>>
>>
>> on x86_64:
>>
>> CONFIG_SND_SOC_WCD9335=m
>> which selects REGMAP_SLIMBUS, but SLIMBUS is not set/enabled.
>>
>>
>> ERROR: "slim_driver_unregister" [sound/soc/codecs/snd-soc-wcd9335.ko] undefined!
>> ERROR: "__slim_driver_register" [sound/soc/codecs/snd-soc-wcd9335.ko] undefined!
>> ERROR: "slim_read" [drivers/base/regmap/regmap-slimbus.ko] undefined!
>> ERROR: "slim_write" [drivers/base/regmap/regmap-slimbus.ko] undefined!
>>
>>
>> Full randconfig file is attached.
>>


-- 
~Randy

  reply	other threads:[~2019-01-29 17:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-29  6:11 linux-next: Tree for Jan 29 Stephen Rothwell
2019-01-29 16:30 ` linux-next: Tree for Jan 29 (net/ipv4/devinet.c) Randy Dunlap
2019-01-29 16:50 ` linux-next: Tree for Jan 29 (SLIMbus & SND_SOC_WCD9335) Randy Dunlap
2019-01-29 16:57   ` Srinivas Kandagatla
2019-01-29 17:00     ` Randy Dunlap [this message]
2019-01-29 17:04 ` linux-next: Tree for Jan 29 (security/safesetid/) Randy Dunlap
2019-01-29 18:21   ` Micah Morton
2019-01-29 18:54     ` [PATCH] LSM: SafeSetID: 'depend' on CONFIG_SECURITY mortonm
2019-01-29 19:52       ` James Morris
2019-01-29 17:17 ` linux-next: Tree for Jan 29 (security/integrity/) 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=7f4aa68d-d9ee-ec08-8593-a975a999e5e2@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=srinivas.kandagatla@linaro.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 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).