From: Andrew Walrond <andrew@walrond.org>
To: sparclinux@vger.kernel.org
Subject: Re: Sparc-2.6.24 GIT tree
Date: Mon, 06 Aug 2007 08:38:22 +0000 [thread overview]
Message-ID: <46B6DDFE.6060203@walrond.org> (raw)
In-Reply-To: <20070805.180930.21926239.davem@davemloft.net>
David Miller wrote:
> I cut a 2.6.24 sparc development tree at:
>
> kernel.org:/pub/scm/linux/kernel/git/davem/sparc-2.6.24.git
>
> merely because I wanted to dump some framebuffer driver changes
> out of my inbox that were not appropriate for 2.6.23
>
I've been trying to upgrade the 2.6.20 kernel on a T1000 to a vanilla
2.6.22.1 kernel, but have so far failed to build a kernel that will boot
cleanly. (I used make oldconfig on the 2.6.20 .config + lots of minor
variations).
Will I have better luck if I follow one or more of your trees, David?
Which tree is best to follow? Could you give a quick overview of your
trees and how they fit in with upstream (or point me to an FAQ if there
is one).
Or, if 2.6.22.1 should boot fine on a T1000, perhaps someone could mail
me a known good .config that I could use as a base?
Thanks!
Andrew Walrond
next prev parent reply other threads:[~2007-08-06 8:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 1:09 Sparc-2.6.24 GIT tree David Miller
2007-08-06 8:38 ` Andrew Walrond [this message]
2007-08-06 9:31 ` David Miller
2007-08-06 9:32 ` David Miller
2007-08-06 10:26 ` Andrew Walrond
2007-08-06 15:46 ` Andrew Walrond
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=46B6DDFE.6060203@walrond.org \
--to=andrew@walrond.org \
--cc=sparclinux@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.