All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Make spitz compile again
Date: Tue, 1 Nov 2005 21:05:17 +0100	[thread overview]
Message-ID: <20051101200516.GA7172@elf.ucw.cz> (raw)
In-Reply-To: <1130773530.8353.39.camel@localhost.localdomain>

Hi!

> > This is what I needed to do after update to latest linus
> > kernel. Perhaps it helps someone. 
> > 
> > Signed-off-by: Pavel Machek <pavel@suse.cz>
> > 
> > , but it is against Richard's tree merged into my tree, so do not
> > expect to apply it over mainline. Akita code movement is needed if I
> > want to compile kernel without akita support...
> 
> This is an update of my tree against 2.6.14-git3:
> 
> http://www.rpsys.net/openzaurus/temp/total-2.6.14-git3-r0.patch.gz

I did compile fixing, but it still will not boot. With neither my
config, not with yours. Just blank screen. Any ideas?

> http://www.rpsys.net/openzaurus/temp/total-2.6.14-git3-r0-defconfig-cxx00

								Pavel
-- 
Thanks, Sharp!

  parent reply	other threads:[~2005-11-01 20:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-31 13:42 Make spitz compile again Pavel Machek
2005-10-31 15:45 ` Richard Purdie
2005-11-01 19:31   ` Pavel Machek
2005-11-01 20:10     ` Richard Purdie
2005-11-01 20:37       ` Pavel Machek
2005-11-01 20:39       ` Pavel Machek
2005-11-01 20:40       ` Pavel Machek
2005-11-01 20:05   ` Pavel Machek [this message]
2005-11-01 20:19     ` Richard Purdie
2005-11-01 21:46     ` Richard Purdie
2005-11-01 22:14       ` Russell King
2005-11-01 22:54         ` Richard Purdie
2005-11-02 11:10       ` Pavel Machek
2005-11-02 12:51   ` Pavel Machek
2005-11-02 13:47     ` Richard Purdie
2005-11-02 13:52       ` Pavel Machek
2005-11-02 14:44         ` Richard Purdie
2005-10-06  7:16           ` spitz autorepeat Pavel Machek

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=20051101200516.GA7172@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpurdie@rpsys.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 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.