All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jun Sun <jsun@mvista.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Ralf Baechle <ralf@oss.sgi.com>, Ladislav Michl <ladis@psi.cz>,
	linux-mips@oss.sgi.com
Subject: Re: [patch] linux: DBE/IBE handling rewrite
Date: Thu, 27 Jun 2002 12:08:23 -0700	[thread overview]
Message-ID: <3D1B62A7.6010600@mvista.com> (raw)
In-Reply-To: Pine.GSO.3.96.1020627193348.21496G-100000@delta.ds2.pg.gda.pl

Maciej W. Rozycki wrote:

> On Thu, 27 Jun 2002, Jun Sun wrote:
> 
> 
>>You missed the point - I like to see some open discussions before any big 
>>changes to MIPS.  If you look back of all the significant changes made to the 
>>
> 
>  Agreed.
> 
> 
>>MIPS tree, you will see a high percentage of them went in without any open 
>>
> 
>  I can't actually recall any significant changes recently (barring
> platform additions I don't really track), certainly not since 2.4.  All I
> observe are bug fixes, clean-ups and similar stuff.
> 


Here are some of those on top of my mind.  And I am pretty sure I am missing 
others:

1) /proc/cpuinfo and some bootinfo.h change  (I think these two come from one 
change)
2) split of cache and tlb files
3) some kind of flush_cache_LSB() routines.


> 
>>discussion or pre-warning.  It is this context that brought out :-(.  Not your 
>>patch per se.
>>
> 
>  If you suggest that this change qualifies as big, then I'd write you
> exaggerate. 


It is not big logically.  However, outside all the boards that are in oss 
tree, I can safely say there are at least twenty MIPS porting efforts going on 
at various stages.  Next time those people sync up with oss, they will find 
the missing symbol of bus_error_init().


 Anyway, I've sent a proposed function and then a real
> implementation of bits that were broken "since forever".  Even the
> previous clean-up, for 32-bit MIPS solely, was written by me -- apparently
> nobody else was interested in the subsystem.
> 


It wasn't my intention to dampen your MIPS contribution.  In fact, I start to 
regret about my first email which now looks a little irresponsible.

If anything out of this thread can increase the awareness of open discussion 
and awareness of the existence of many boards which are not part of oss tree 
yet, I shall be happy.


Jun

  reply	other threads:[~2002-06-27 19:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-17 11:33 DBE/IBE handling incompatibility Ladislav Michl
2002-06-19 16:47 ` Maciej W. Rozycki
2002-06-25  0:36   ` Ladislav Michl
2002-06-25 11:55     ` Maciej W. Rozycki
2002-06-26 11:51       ` [patch] linux: DBE/IBE handling rewrite Maciej W. Rozycki
2002-06-26 12:05         ` Ralf Baechle
2002-06-26 13:07           ` Maciej W. Rozycki
2002-06-26 17:21             ` Jun Sun
2002-06-27 12:00               ` Maciej W. Rozycki
2002-06-27 17:12                 ` Jun Sun
2002-06-27 18:29                   ` Maciej W. Rozycki
2002-06-27 19:08                     ` Jun Sun [this message]
2002-06-27 20:00                       ` Maciej W. Rozycki
2002-06-26 20:59             ` [patch] GIO bus support Ladislav Michl
2002-06-26 23:46               ` Ralf Baechle
2002-06-27 10:14                 ` FIR problem jeff
2002-06-27 10:14                   ` jeff
2002-06-27 12:21               ` [patch] GIO bus support Maciej W. Rozycki
2002-08-04 22:03                 ` Ladislav Michl
2002-09-28 19:55                 ` Ladislav Michl
2002-06-26 17:17         ` [patch] linux: DBE/IBE handling rewrite Jun Sun
2002-06-27 11:51           ` Maciej W. Rozycki

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=3D1B62A7.6010600@mvista.com \
    --to=jsun@mvista.com \
    --cc=ladis@psi.cz \
    --cc=linux-mips@oss.sgi.com \
    --cc=macro@ds2.pg.gda.pl \
    --cc=ralf@oss.sgi.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 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.