public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Pavel Machek <pavel@ucw.cz>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Make spitz compile again
Date: Tue, 01 Nov 2005 22:54:53 +0000	[thread overview]
Message-ID: <1130885693.8489.50.camel@localhost.localdomain> (raw)
In-Reply-To: <20051101221410.GA21034@flint.arm.linux.org.uk>

On Tue, 2005-11-01 at 22:14 +0000, Russell King wrote: 
> On Tue, Nov 01, 2005 at 09:46:52PM +0000, Richard Purdie wrote:
> > I'd be interested to know if this helps your spitz kernel as its gets
> > c7x0 working again. Obviously the next step is to work out why this
> > breaks things but reverting it gets my Zaurus dev tree working again
> > which stops users c7x0 complaining :)
> 
> You need to at least follow my suggestion in order to move forward on
> this.  You're the only ones seeing a problem so far.

I realise that and I will debug this when I have time to do so. At least
that patch identifies roughly where the problem is and allows me to
think about merging more code now my dev tree works again.

I passed the patch on to Pavel in the hope that it might solve his
immediate problem and give him a clue as to where to look for the real
solution if it does. 

> Maybe when other folk try it out some pattern will emerge.
> 
> Shame this couldn't have been done a month ago though when I wrote the
> patch and it was fresh in my mind.

It is as I could have spent the time merging more Zaurus support instead
of chasing bugs. Several Zaurus related things I'd like to have seen
merged in 2.6.15 are looking unlikely to happen due to time
constraints :-(.

Richard



  reply	other threads:[~2005-11-01 22:55 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
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 [this message]
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=1130885693.8489.50.camel@localhost.localdomain \
    --to=rpurdie@rpsys.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rmk+lkml@arm.linux.org.uk \
    /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