From: Artem Bityutskiy <dedekind1@gmail.com>
To: manjugk@ti.com
Cc: linux-omap@vger.kernel.org, khilman@deeprootsystems.com
Subject: Re: [PATCH] [OMAP3_PM] Fix zoom2 defconfig build
Date: Mon, 02 Nov 2009 10:26:10 +0200 [thread overview]
Message-ID: <1257150370.29885.986.camel@localhost> (raw)
In-Reply-To: <1257148563-18604-1-git-send-email-manjugk@ti.com>
On Mon, 2009-11-02 at 13:26 +0530, manjugk@ti.com wrote:
> From: Manjunatha GK <manjugk@ti.com>
>
>
> Signed-off-by: Manjunatha GK <manjugk@ti.com>
> ---
> arch/arm/configs/omap_zoom2_defconfig | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/configs/omap_zoom2_defconfig b/arch/arm/configs/omap_zoom2_defconfig
> index f1739fa..8ca835a 100644
> --- 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.
--
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
next prev parent reply other threads:[~2009-11-02 8:26 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 [this message]
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
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=1257150370.29885.986.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 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.