From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: alsa-devel@alsa-project.org, kernel-janitors@vger.kernel.org
Subject: Re: sound/soc/codecs/wm2200.c:2082:2: error: unknown field 'num_ranges' specified in initializer
Date: Sat, 6 Oct 2012 09:51:43 +0100 [thread overview]
Message-ID: <20121006085141.GA8590@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20121006012304.GB11046@localhost>
On Sat, Oct 06, 2012 at 09:23:04AM +0800, Fengguang Wu wrote:
> All error/warnings:
> sound/soc/codecs/wm2200.c:2082:2: error: unknown field 'num_ranges' specified in initializer
Not a real error (nor is anything else like this in my trees right now),
all the branches will be rebased after the merge window which will pull
in the dependencies.
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: alsa-devel@alsa-project.org, kernel-janitors@vger.kernel.org
Subject: Re: sound/soc/codecs/wm2200.c:2082:2: error: unknown field 'num_ranges' specified in initializer
Date: Sat, 06 Oct 2012 08:51:43 +0000 [thread overview]
Message-ID: <20121006085141.GA8590@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20121006012304.GB11046@localhost>
On Sat, Oct 06, 2012 at 09:23:04AM +0800, Fengguang Wu wrote:
> All error/warnings:
> sound/soc/codecs/wm2200.c:2082:2: error: unknown field 'num_ranges' specified in initializer
Not a real error (nor is anything else like this in my trees right now),
all the branches will be rebased after the merge window which will pull
in the dependencies.
next prev parent reply other threads:[~2012-10-06 8:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-06 1:23 sound/soc/codecs/wm2200.c:2082:2: error: unknown field 'num_ranges' specified in initializer Fengguang Wu
2012-10-06 8:51 ` Mark Brown [this message]
2012-10-06 8:51 ` 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=20121006085141.GA8590@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=fengguang.wu@intel.com \
--cc=kernel-janitors@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.