From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Anca Emanuel <anca.emanuel@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: linux-next: Tree for December 29
Date: Wed, 29 Dec 2010 13:08:03 +0000 [thread overview]
Message-ID: <20101229130802.GA20306@sirena.org.uk> (raw)
In-Reply-To: <AANLkTikPbkM4ccO-2=+TSJN6dR64ibTReSsYYdhLYrUt@mail.gmail.com>
On Wed, Dec 29, 2010 at 12:45:35PM +0200, Anca Emanuel wrote:
> >> ? MODPOST 2808 modules
> >> ERROR: "__tracepoint_snd_soc_jack_irq"
> >> [sound/soc/codecs/snd-soc-wm8994.ko] undefined!
> >> ERROR: "__tracepoint_snd_soc_jack_irq"
> >> [sound/soc/codecs/snd-soc-wm8350.ko] undefined!
> >> ERROR: "__tracepoint_snd_soc_jack_irq"
> >> [sound/soc/codecs/snd-soc-88pm860x.ko] undefined!
> >> WARNING: modpost: Found 59 section mismatch(es).
> >> To see full details build your kernel with:
> >> 'make CONFIG_DEBUG_SECTION_MISMATCH=y'
> >> make[2]: *** [__modpost] Error 1
> >> make[1]: *** [modules] Error 2
> > It would be good if you could publish your config files with these
> > reports. ?I have cc'd this to those who may be able to fix this.
*Please* do always CC maintainers on reports and always include the
config like Stephen requested, build errors without reproduction
information are typically no use.
I've probably fixed this; I've not fully explored this as even a noop
build of the config you provided on my laptop is taking many minutes.
next prev parent reply other threads:[~2010-12-29 13:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-29 2:07 linux-next: Tree for December 29 Stephen Rothwell
2010-12-29 6:41 ` Anca Emanuel
2010-12-29 8:58 ` Anca Emanuel
2010-12-29 9:46 ` Stephen Rothwell
2010-12-29 10:45 ` Anca Emanuel
2010-12-29 13:08 ` Mark Brown [this message]
2010-12-29 9:54 ` Sedat Dilek
2010-12-29 10:00 ` Stephen Rothwell
2010-12-29 16:53 ` linux-next: Tree for December 29 (netfilter build errors) Randy Dunlap
2010-12-30 2:10 ` Shan Wei
2010-12-30 2:18 ` Changli Gao
2010-12-30 16:47 ` Sedat Dilek
2010-12-30 17:07 ` Eric Dumazet
-- strict thread matches above, loose matches on Subject: below --
2009-12-29 0:28 linux-next: Tree for December 29 Stephen Rothwell
2008-12-29 16:16 Stephen Rothwell
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=20101229130802.GA20306@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=anca.emanuel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--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