From: Eugene Surovegin <ebs@ebshome.net>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: Andrew Morton <akpm@osdl.org>,
"Gala Kumar K.-galak" <galak@freescale.com>,
linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH 00/14] ppc32: Remove board ports that are no longer maintained
Date: Tue, 30 Aug 2005 00:44:47 -0700 [thread overview]
Message-ID: <20050830074447.GC27899@gate.ebshome.net> (raw)
In-Reply-To: <0048AEBE-072F-4250-9D32-EC019D0BDBB9@freescale.com>
On Mon, Aug 29, 2005 at 08:46:22PM -0500, Kumar Gala wrote:
>
> On Jul 27, 2005, at 2:57 PM, Andrew Morton wrote:
>
> >Kumar Gala <galak@freescale.com> wrote:
> >
> >>
> >>The following board ports are no longer maintained or have become
> >> obsolete:
> >>
> >> adir
> >> ash
> >> beech
> >> cedar
> >> ep405
> >> k2
> >> mcpn765
> >> menf1
> >> oak
> >> pcore
> >> rainier
> >> redwood
> >> sm850
> >> spd823ts
> >>
> >> We are there for removing support for them.
> >>
> >
> >I'll merge all these into -mm for now, but will hold off sending
> >any of
> >them upstream pending confirmation of which patches we really want to
> >proceed with.
>
> No one has screamed about anything but ep405 so all the others should
> go to Linus now.
Matt told me he would probably get ash soon. There is even a path in
the -mm queue which should fix ethernet on this board.
Matt?
--
Eugene
prev parent reply other threads:[~2005-08-30 7:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 15:32 [PATCH 00/14] ppc32: Remove board ports that are no longer maintained Kumar Gala
2005-07-27 16:13 ` Michael Richardson
2005-07-27 16:27 ` Eugene Surovegin
2005-07-27 17:15 ` Matt Porter
2005-07-27 23:34 ` Kumar Gala
2005-07-29 16:33 ` Michael Richardson
2005-07-29 17:03 ` Esben Nielsen
2005-07-29 18:10 ` Kumar Gala
2005-07-27 19:57 ` Andrew Morton
2005-07-27 23:35 ` Kumar Gala
2005-07-31 16:39 ` Kumar Gala
2005-08-30 1:46 ` Kumar Gala
2005-08-30 7:44 ` Eugene Surovegin [this message]
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=20050830074447.GC27899@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=akpm@osdl.org \
--cc=galak@freescale.com \
--cc=kumar.gala@freescale.com \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).