From: Ingo Molnar <mingo@elte.hu>
To: Gene Heskett <gene.heskett@gmail.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-kbuild@vger.kernel.org
Subject: Re: 2.6.36, make oldconfig broken
Date: Sat, 23 Oct 2010 15:41:02 +0200 [thread overview]
Message-ID: <20101023134102.GA7893@elte.hu> (raw)
In-Reply-To: <201010221608.36754.gene.heskett@gmail.com>
hi Gene,
* Gene Heskett <gene.heskett@gmail.com> wrote:
> > Please send your 2.6.35.7 .config file so that we can generate & see the
> > changes.
>
> Attached Randy, & many thanks.
>
> Just for S&G I overwrote the generated .config in the 2.6.36 tree with these
> files, and ran a make xconfig, which bitched about line 3109, and which I don't
> recall ever playing with, "RAR_REGISTER" IIRC, so I saved it without any other
> changes and built/installed & booted from that now.
In case it's useful: i take old .config's and put them into new kernels all the
time, and i very much depend on configured drivers and options not going away
suddenly. I know lots of other developers depend on that as well.
In the hundreds or so cases i've done this manually in the past few years i only
remember less than 5 cases where this didnt work in an 'as expected' way.
So this should really work for you. If it doesnt when going from 2.6.35 to 2.6.36
then that's very likely a bug somewhere which we want to fix ...
Thanks,
Ingo
next prev parent reply other threads:[~2010-10-23 13:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 16:29 Re:2.6.36, make oldconfig broken Gene Heskett
2010-10-22 18:40 ` 2.6.36, " Randy Dunlap
2010-10-22 20:08 ` Gene Heskett
2010-10-22 21:20 ` Randy Dunlap
2010-10-23 0:54 ` Gene Heskett
2010-10-23 1:39 ` Ken Moffat
2010-10-23 2:43 ` Gene Heskett
2010-10-24 1:36 ` Randy Dunlap
2010-10-24 5:13 ` Gene Heskett
2010-10-25 14:23 ` Gene Heskett
2010-10-23 1:07 ` Ken Moffat
2010-10-23 2:18 ` Gene Heskett
2010-10-23 13:41 ` Ingo Molnar [this message]
2010-10-23 16:26 ` Gene Heskett
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=20101023134102.GA7893@elte.hu \
--to=mingo@elte.hu \
--cc=gene.heskett@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.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