From: Artem Bityutskiy <dedekind1@gmail.com>
To: "G, Manjunath Kondaiah" <manjugk@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"khilman@deeprootsystems.com" <khilman@deeprootsystems.com>
Subject: RE: [PATCH] [OMAP3_PM] Fix zoom2 defconfig build
Date: Mon, 02 Nov 2009 11:17:17 +0200 [thread overview]
Message-ID: <1257153437.17890.0.camel@localhost> (raw)
In-Reply-To: <E0D41E29EB0DAC4E9F3FF173962E9E940254037933@dbde02.ent.ti.com>
On Mon, 2009-11-02 at 14:30 +0530, G, Manjunath Kondaiah wrote:
> > > --- a/arch/arm/configs/omap_zoom2_defconfig
> > > +++ b/arch/arm/configs/omap_zoom2_defconfig
> > > @@ -1350,7 +1350,7 @@ CONFIG_ENABLE_MUST_CHECK=y
> > > CONFIG_FRAME_WARN=1024
> > > CONFIG_MAGIC_SYSRQ=y
> > > # CONFIG_UNUSED_SYMBOLS is not set
> > > -# CONFIG_DEBUG_FS is not set
> > > +CONFIG_DEBUG_FS=y
> > > # CONFIG_HEADERS_CHECK is not set
> > > CONFIG_DEBUG_KERNEL=y
> > > # CONFIG_DEBUG_SHIRQ is not set
> >
> > It is nicer to provide the build failure log. But if this is a build
> > failure, this means there is a problem with Kconfig dependency, which
> > should be fixed properly, not hidden.
>
> Here is build failure log:
> MODPOST vmlinux.o
> WARNING: modpost: Found 1 section mismatch(es).
> To see full details build your kernel with:
> 'make CONFIG_DEBUG_SECTION_MISMATCH=y'
> GEN .version
> CHK include/linux/compile.h
> UPD include/linux/compile.h
> CC init/version.o
> LD init/built-in.o
> LD .tmp_vmlinux1
> arch/arm/mach-omap2/built-in.o: In function `omap_sram_idle':
> /home/manju/clones/git/linux-omap-pm/arch/arm/mach-omap2/pm34xx.c:441: undefined reference to `pm_dbg_regset_save'
> /home/manju/clones/git/linux-omap-pm/arch/arm/mach-omap2/pm34xx.c:452: undefined reference to `pm_dbg_regset_save'
> arch/arm/mach-omap2/built-in.o: In function `configure_vc':
> /home/manju/clones/git/linux-omap-pm/arch/arm/mach-omap2/pm34xx.c:1226: undefined reference to `pm_dbg_regset_init'
> /home/manju/clones/git/linux-omap-pm/arch/arm/mach-omap2/pm34xx.c:1227: undefined reference to `pm_dbg_regset_init'
> make: *** [.tmp_vmlinux1] Error 1
>
> The above two API's are under CONFIG_DEBUG_FS flag in arch/arm/mach-omap2/pm-debug.c
OK, but why do you send a band-aid to fix this, instead of a real fix?
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-11-02 9:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 7:56 [PATCH] [OMAP3_PM] Fix zoom2 defconfig build manjugk
2009-11-02 7:59 ` G, Manjunath Kondaiah
2009-11-02 8:26 ` Artem Bityutskiy
2009-11-02 9:00 ` G, Manjunath Kondaiah
2009-11-02 9:14 ` Felipe Balbi
2009-11-02 10:00 ` G, Manjunath Kondaiah
2009-11-02 16:09 ` Kevin Hilman
2009-11-02 16:30 ` G, Manjunath Kondaiah
2009-11-02 17:10 ` Kevin Hilman
2009-11-02 9:17 ` Artem Bityutskiy [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=1257153437.17890.0.camel@localhost \
--to=dedekind1@gmail.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=manjugk@ti.com \
/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