From: Andrew Morton <akpm@osdl.org>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: len.brown@intel.com, linux-kernel@vger.kernel.org
Subject: Re: 2.6.16-rc4-mm2 configs
Date: Sun, 26 Feb 2006 20:50:28 -0800 [thread overview]
Message-ID: <20060226205028.789b9ca7.akpm@osdl.org> (raw)
In-Reply-To: <20060226195531.ee1ca136.rdunlap@xenotime.net>
"Randy.Dunlap" <rdunlap@xenotime.net> wrote:
>
> On Sun, 26 Feb 2006 19:51:09 -0800 Andrew Morton wrote:
>
> > "Brown, Len" <len.brown@intel.com> wrote:
> > >
> > >
> > > >> a. why does SONY_ACPI default to m ? Other similar options
> > > >are default n.
> > > >
> > > >Because I got heartily sick of losing the setting each time I
> > > >went back to a mainline kernel and did `make oldconfig'.
> > >
> > > IIR the recommendation from Roman on these things was
> > > to remove the default entirely. If you have a favorite
> > > .config file with =m in it, then make oldconfig should
> > > preserve that choice.
> > >
> >
> > Nope. Once you remove the Kconfig entry entirely (ie: go back to a
> > mainline kernel), `make oldconfig' will rub that config entry out
> > completely.
>
> Yes. So you have it =m so that it will build in your
> test builds, right? or some other reason?
>
As I said, I got tired of losing the setting and not being able to control
the backlight brightness. <insert anecdote about sitting outside at son's
basketball game, having to recompile entire kernel by smell so I could read
the screen>
next prev parent reply other threads:[~2006-02-27 4:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-27 2:47 Brown, Len
2006-02-27 3:51 ` Andrew Morton
2006-02-27 3:55 ` Randy.Dunlap
2006-02-27 4:50 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-27 7:28 Brown, Len
2006-02-27 1:09 Randy.Dunlap
2006-02-27 1:59 ` Andrew Morton
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=20060226205028.789b9ca7.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®