From: Doug Anderson <dianders@chromium.org>
To: Olof Johansson <olof@lixom.net>
Cc: Kukjin Kim <kgene.kim@samsung.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: exynos: defconfig update
Date: Thu, 9 May 2013 15:07:25 -0700 [thread overview]
Message-ID: <CAD=FV=VMCLk0h0XxJv1Q3EkpottVkpwKEa87McmmipdJA7TN+A@mail.gmail.com> (raw)
In-Reply-To: <1368133099-16997-1-git-send-email-olof@lixom.net>
Olof,
On Thu, May 9, 2013 at 1:58 PM, Olof Johansson <olof@lixom.net> wrote:
> +CONFIG_ZBOOT_ROM_TEXT=0x0
> +CONFIG_ZBOOT_ROM_BSS=0x0
Probably these aren't needed, but don't hurt since the default is 0.
This seems to pop up a lot since there are lots of legacy configs that
have 0x0 here.
Either with or without that fixup, this looks reasonable to me.
Reviewed-by: Doug Anderson <dianders@chromium.org>
WARNING: multiple messages have this Message-ID (diff)
From: dianders@chromium.org (Doug Anderson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: exynos: defconfig update
Date: Thu, 9 May 2013 15:07:25 -0700 [thread overview]
Message-ID: <CAD=FV=VMCLk0h0XxJv1Q3EkpottVkpwKEa87McmmipdJA7TN+A@mail.gmail.com> (raw)
In-Reply-To: <1368133099-16997-1-git-send-email-olof@lixom.net>
Olof,
On Thu, May 9, 2013 at 1:58 PM, Olof Johansson <olof@lixom.net> wrote:
> +CONFIG_ZBOOT_ROM_TEXT=0x0
> +CONFIG_ZBOOT_ROM_BSS=0x0
Probably these aren't needed, but don't hurt since the default is 0.
This seems to pop up a lot since there are lots of legacy configs that
have 0x0 here.
Either with or without that fixup, this looks reasonable to me.
Reviewed-by: Doug Anderson <dianders@chromium.org>
next prev parent reply other threads:[~2013-05-09 22:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 20:58 [PATCH] ARM: exynos: defconfig update Olof Johansson
2013-05-09 20:58 ` Olof Johansson
2013-05-09 22:07 ` Doug Anderson [this message]
2013-05-09 22:07 ` Doug Anderson
2013-05-10 6:55 ` Tushar Behera
2013-05-10 6:55 ` Tushar Behera
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='CAD=FV=VMCLk0h0XxJv1Q3EkpottVkpwKEa87McmmipdJA7TN+A@mail.gmail.com' \
--to=dianders@chromium.org \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
/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.