linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Xiong Zhou <jencce.kernel@gmail.com>
Cc: Peter Hurley <peter@hurleysoftware.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org
Subject: Re: [PATCH -next] sound/soc/codecs: Mark snd-soc-wm2200 and snd-soc-wm-adsp as BROKEN
Date: Sat, 30 Mar 2013 13:52:13 +0000	[thread overview]
Message-ID: <20130330135212.GN18316@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1303302029231.25958@M2420>

[-- Attachment #1: Type: text/plain, Size: 1535 bytes --]

On Sat, Mar 30, 2013 at 08:30:39PM +0800, Xiong Zhou wrote:

> So the failure comes. Yes, this config is kind of specific, not much.

Right, but look at what the options are doing - ALL_CODECS is purely for
build coverage so someone seeing the issue in this form must be running
a partial build coverage test which happens to cover a relatively
obscure subsystem.  This is why none of the all*configs that are run on
-next as standard fail.

> The definition of one array which is cited by one module comes in 
> another module, and this dependence does not appear in Kconfig 
> architecture. Indeed, the help text of ALL_CODECS reminds the 
> separated surpporting bus options. Still I think this is unreasonable.
> Even though build coverage test is the only proper purpose. It breaks
> the whole building procedure.

I'm not saying this doesn't need to be fixed, I'm saying we need a sane
fix.

> I think copying the same array definition across c file is ugly, and Mark
> said that this is not a Kconfig issue. So far, I have not got any other
> idea to fix this. Code cruising.

I actually looked at this earlier and sent a fix for it (didn't get
round to mailing this thread yet, sorry), the code wouldn't have worked
at all for WM2200 - this is the sort of thing that should be apparent as
soon as people start asking questions like "why was this dependency
added, is it sensible?" which should be among the first questions asked
when turning up something like this, especially for recent changes.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2013-03-30 13:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-29 14:12 [PATCH -next] sound/soc/codecs: Mark snd-soc-wm2200 and snd-soc-wm-adsp as BROKEN Peter Hurley
2013-03-29 17:12 ` Mark Brown
2013-03-29 18:45   ` Peter Hurley
2013-03-29 18:50     ` Mark Brown
2013-03-30 12:30       ` Xiong Zhou
2013-03-30 13:52         ` 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=20130330135212.GN18316@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=jencce.kernel@gmail.com \
    --cc=linux-next@vger.kernel.org \
    --cc=peter@hurleysoftware.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;
as well as URLs for NNTP newsgroup(s).