linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>,
	moderated for non-subscribers <alsa-devel@alsa-project.org>,
	Takashi Iwai <tiwai@suse.de>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: linux-next: Tree for Feb 13 (sound/soc/codecs/snd-soc-ab8500-codec)
Date: Thu, 13 Feb 2020 09:41:16 -0800	[thread overview]
Message-ID: <d0d9a245-f336-1334-90a8-631faf95d071@infradead.org> (raw)
In-Reply-To: <d8dbd288-5270-42f1-0d55-b0f1516addb1@infradead.org>

On 2/13/20 9:06 AM, Randy Dunlap wrote:
> On 2/12/20 7:52 PM, Stephen Rothwell wrote:
>> Hi all,
>>
>> 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!
> 
> 
> Full randconfig file is attached.
> 
> 

[adding Geert, dropping 3 ST people due to bounced email addresses]

-- 
~Randy


  reply	other threads:[~2020-02-13 17:41 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 [this message]
2020-02-13 19:31     ` 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=d0d9a245-f336-1334-90a8-631faf95d071@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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).