From: Dmitri Vorobiev <dmitri.vorobiev@gmail.com>
To: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH -v2][MIPS] Add Atlas to feature-removal-schedule.txt
Date: Tue, 15 Jan 2008 02:24:58 +0300 [thread overview]
Message-ID: <478BEF4A.80805@gmail.com> (raw)
Ralf Baechle on Atlas board support in the linux-mips mailing list:
> Maciej is promising to fix it up since a few years ;-) Aside of that it's
> safe to say the Atlas is dead like a coffin nail.
Signed-off-by: Dmitri Vorobiev <dmitri.vorobiev@gmail.com>
---
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index 20c4c8b..2693ebc 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -333,3 +333,11 @@ Why: This driver has been marked obsolet
Who: Stephen Hemminger <shemminger@linux-foundation.org>
---------------------------
+
+What: Support for MIPS Technologies' Atlas evaluation board
+When: March 2008
+Why: Apparently there is no user base left for this platform.
+ Hardware out of production since several years.
+Who: Dmitri Vorobiev <dmitri.vorobiev@gmail.com>
+
+---------------------------
reply other threads:[~2008-01-14 23:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=478BEF4A.80805@gmail.com \
--to=dmitri.vorobiev@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@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