From: Randy Dunlap <randy.dunlap@oracle.com>
To: Gene Heskett <gene.heskett@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-kbuild@vger.kernel.org
Subject: Re: 2.6.36, make oldconfig broken
Date: Fri, 22 Oct 2010 11:40:19 -0700 [thread overview]
Message-ID: <20101022114019.60839ff2.randy.dunlap@oracle.com> (raw)
In-Reply-To: <201010221229.36996.gene.heskett@gmail.com>
On Fri, 22 Oct 2010 12:29:36 -0400 Gene Heskett wrote:
[adding linux-kbuild]
> Greets all;
>
> I have managed to get 2.6.36 to a semi-usable state, but I have major
> breakage yet.
>
> Question: what happens if I simply move my working 2.6.35.7 .config into the
> 2.6.36 tree and build it from that?
I think that it runs 'make oldconfig' automatically for you.
> It can't be any worse than what the broken 'make oldconfig' did to it. What
> it output changed the disk drivers, graphic card drivers and just plain
> threw away at least a hundred lines in the multimedia drivers section.
>
> How do you suggest I recover from this if just building from the 2.6.35.7
> .conf doesn't work?
Please send your 2.6.35.7 .config file so that we can generate & see the
changes.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-10-22 18: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 ` Randy Dunlap [this message]
2010-10-22 20:08 ` 2.6.36, " 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
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=20101022114019.60839ff2.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=gene.heskett@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 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.