From: chanho.min@lge.com (Chanho Min)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64:kconfig: make default for CONFIG_COMPAT
Date: Tue, 15 Apr 2014 19:41:53 +0900 [thread overview]
Message-ID: <007001cf5897$533c23f0$f9b46bd0$@min@lge.com> (raw)
In-Reply-To: <4386453.rooF7jKWKy@wuerfel>
> On Tuesday 15 April 2014 09:07:00 Chanho Min wrote:
> > > -----Original Message-----
> > > From: Will Deacon [mailto:will.deacon at arm.com]
> > > Sent: Tuesday, April 15, 2014 1:46 AM
> > > To: Chanho Min
> > > Cc: Catalin Marinas; linux-arm-kernel at lists.infradead.org; linux-kernel at vger.kernel.org
> > > Subject: Re: [PATCH] arm64:kconfig: make default for CONFIG_COMPAT
> > >
> > > On Mon, Apr 14, 2014 at 09:08:03AM +0100, Chanho Min wrote:
> > > > 'make savedefconfig' doesn't generate defconfig properly due to
> > > > missing COMPAT default. So Add default and set to yes.
> > >
> > > I thought a missing `default' line in a Kconfig entry meant that the option
> > > ended up defaulting to 'n'. What exactly is the problem you are seeing?
> >
> > Correct minimal config is not generated without default line.
> > If we want to set COMPAT to 'n', 'default n' should be added.
>
> That would be pointless, because 'n' is already the default.
> What do you want to achieve?
Sorry, It is my mistake. Please ignore this patch.
Chanho
>
> Arnd
prev parent reply other threads:[~2014-04-15 10:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 8:08 [PATCH] arm64:kconfig: make default for CONFIG_COMPAT Chanho Min
2014-04-14 16:46 ` Will Deacon
2014-04-15 0:07 ` Chanho Min
2014-04-15 7:54 ` Arnd Bergmann
2014-04-15 10:41 ` Chanho Min [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='007001cf5897$533c23f0$f9b46bd0$@min@lge.com' \
--to=chanho.min@lge.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).