Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: New randconfig build failure: rx51 asoc / gpiolib
Date: Mon, 20 Jan 2014 17:16:27 +0000	[thread overview]
Message-ID: <20140120171627.GW17314@sirena.org.uk> (raw)
In-Reply-To: <20140117131257.GB15937@n2100.arm.linux.org.uk>

On Fri, Jan 17, 2014 at 01:12:58PM +0000, Russell King - ARM Linux wrote:
> Last night's omap randconfig found this.  This has only appeared in the
> builds in the last few days, so it's a new regression for the changes
> queued up for merge window:

Really?  The relevant change is quite old...  it is possible some other
thing removed a select though so gpiolib can now be unset.

> which is caused by "struct snd_soc_jack_gpio" not being defined.  For
> some reason, this structure is defined in sound/soc.h, but is
> conditionalised upon CONFIG_GPIOLIB.

> This means either the dependencies on SND_OMAP_SOC_RX51 are incorrect
> (they don't include a dependency on GPIOLIB) or ASoC is wrong to make
> the definitions conditional upon GPIOLIB.

I'd add the dependency here.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140120/e6087ac6/attachment.sig>

      reply	other threads:[~2014-01-20 17:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-17 13:12 New randconfig build failure: rx51 asoc / gpiolib Russell King - ARM Linux
2014-01-20 17:16 ` Mark Brown [this message]

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=20140120171627.GW17314@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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