public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Paul Gortmaker <paul.gortmaker@windriver•com>
To: tim.howe@cirrus•com
Cc: broonie@kernel•org, linux-next@vger•kernel.org
Subject: ASoC: cs4349: Add support for Cirrus Logic CS4349 breaks on multiple arch
Date: Sat, 18 Jul 2015 15:28:22 -0400	[thread overview]
Message-ID: <20150718192822.GB4477@windriver.com> (raw)

Hi Tim,

This commit:

e40da86a37f64c73b810bc7a63d77c44dc61accb is the first bad commit
commit e40da86a37f64c73b810bc7a63d77c44dc61accb
Author: Tim Howe <tim.howe@cirrus•com>
Date:   Thu Jul 16 14:51:40 2015 -0500

    ASoC: cs4349: Add support for Cirrus Logic CS4349

    Signed-off-by: Tim Howe <tim.howe@cirrus•com>
    Signed-off-by: Mark Brown <broonie@kernel•org>

is showing up in linux-next build failures for mips, parisc and s390.

sound/soc/codecs/cs4349.c:300:2: error: implicit declaration of function
'devm_gpiod_get_optional' [-Werror=implicit-function-declaration]
sound/soc/codecs/cs4349.c:301:12: error: 'GPIOD_OUT_LOW' undeclared
(first use in this function)
sound/soc/codecs/cs4349.c:306:3: error: implicit declaration of function
'gpiod_set_value_cansleep' [-Werror=implicit-function-declaration]

Here are a few examples:

http://kisskb.ellerman.id.au/kisskb/buildresult/12465322/
http://kisskb.ellerman.id.au/kisskb/buildresult/12465445/
http://kisskb.ellerman.id.au/kisskb/buildresult/12465246/

I'm guessing it needs some tighter Kconfig dependencies to block it
from being selected on arch that don't have/enable gpio stuff.

Paul.

next             reply	other threads:[~2015-07-18 19:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-18 19:28 Paul Gortmaker [this message]
2015-07-18 20:38 ` ASoC: cs4349: Add support for Cirrus Logic CS4349 breaks on multiple arch Fabio Estevam
2015-07-18 21:04   ` Fabio Estevam
2015-07-18 21:16     ` Mark Brown

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=20150718192822.GB4477@windriver.com \
    --to=paul.gortmaker@windriver$(echo .)com \
    --cc=broonie@kernel$(echo .)org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=tim.howe@cirrus$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox