Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Dmitri Vorobiev <dmitri.vorobiev@gmail.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Ralf Baechle <ralf@linux-mips.org>,
	linux-mips@linux-mips.org,
	Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [SPAM] [PATCH][MIPS] Add Atlas to feature-removal-schedule.
Date: Tue, 15 Jan 2008 16:25:11 +0300	[thread overview]
Message-ID: <478CB437.9080006@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64N.0801151156460.23975@blysk.ds.pg.gda.pl>

Maciej W. Rozycki пишет:
> On Tue, 15 Jan 2008, Dmitri Vorobiev wrote:
> 
>>>> +
>>>> +What:	Support for MIPS Technologies' Altas evaluation board
>>>                                                ^^^^^
>>> 					       Atlas
>> This is what happens when doing things in a rush. Thanks, Geert.
> 
>  Hmm, I wonder why you'd be in such a rush to remove my pet project... ;-) 
> The last time I tried it worked; unfortunately I have since been taken 

This was my way of reasoning here:

1) I would like to make a massive cleanup in the arch/mips/mips-boards
   for the reasons explained here:

http://www.linux-mips.org/archives/linux-mips/2008-01/msg00136.html

2) Removing Atlas would reduce the clean-up effort.

3) According to Ralf, the user base for Atlas is zero, the board itself
   is buggy.

4) History knows of an attempt to remove Atlas:

http://www.linux-mips.org/archives/linux-mips/2007-06/msg00153.html

5) Nobody is losing, man-hours are saved. No explanation of why not to do that.
   Hence, the patch to the feature-removal-schedule.txt.

> away my second serial port that I used as a terminal device for the Atlas 
> lying next to me and the first port I have in continuous use.  I'll see if 
> I can give it a hit before March though -- any issues with the port should 
> be minimal.

It would be nice if you could take a look at that (please see the "P.S." part):

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=84c21e254205ecac98f75b01589996440c6a6db0

> 
>   Maciej
> 

  reply	other threads:[~2008-01-15 13:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-14 21:14 [PATCH][MIPS] Add Atlas to feature-removal-schedule Dmitri Vorobiev
2008-01-14 22:02 ` [SPAM] " Geert Uytterhoeven
2008-01-14 23:18   ` Dmitri Vorobiev
2008-01-15 12:03     ` Maciej W. Rozycki
2008-01-15 13:25       ` Dmitri Vorobiev [this message]
2008-01-15 13:57         ` Maciej W. Rozycki
2008-01-15 14:18           ` Dmitri Vorobiev

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=478CB437.9080006@gmail.com \
    --to=dmitri.vorobiev@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@linux-mips.org \
    --cc=ralf@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox