public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Matt Porter <mporter@kernel•crashing.org>
To: Kumar Gala <kumar.gala@freescale•com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs•org>,
	Linux PPC Embedded list <linuxppc-embedded@ozlabs•org>
Subject: Re: Getting ownership for various boards/platforms configs
Date: Thu, 2 Jun 2005 17:18:22 -0700	[thread overview]
Message-ID: <20050602171822.G24818@cox.net> (raw)
In-Reply-To: <bf0d9d49e4c115e67aa5df39e33017a1@freescale.com>; from kumar.gala@freescale.com on Thu, Jun 02, 2005 at 06:19:11PM -0500

On Thu, Jun 02, 2005 at 06:19:11PM -0500, Kumar Gala wrote:
> One issue that comes up from time to time is knowing who to contact 
> about some of the various boards that are supported for PPC.  I've 
> suggested in the past that we create a MAINTAINERS file in 
> arch/ppc/platforms.  I've started with a list of all the _defconfigs 
> that we have and would like to see if we can get contacts for the 
> boards.  All this list is meant to be is a contact point.
> 
> The following is the list, I'll keep a live copy at 
> http://gate.crashing.org/~galak/platform-owners.  Once it gets flushed 
> out I'll turn it into file that looks more like the toplevel 
> MAINTAINERS file.  If we dont have any owners for a board we can 
> discuss if support for it should be removed.  Please email me if you 
> feel you are the owner of any board/config.
> 
> thanks
> 
> - kumar
> 
> ash
> beech

These are't in 2.6, remove the defconfig

> bubinga

me/ebs

> cedar

This isn't in 2.6, remove the defconfig

> ebony

me/ebs

> k2

I did the original port, now unmaintained/obsolete..die die die.

> lopec

trini is probably the maintainer here...he likes this board.

> luan

me

> menf1			Dead (Matt Porter)

Remove it, yes.

> oak

I think it's time to remove it...unmaintained.

> ocotea

me/ebs

> rainier

Not in 2.6...remove defconfig

> redwood5
> redwood6

um...dfarnsworth, want them formally?

> redwood

Not in 2.6...remove defconfig

> stx_gp3

me

> sycamore

me

> walnut

me

  parent reply	other threads:[~2005-06-03  0:18 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-02 23:19 Getting ownership for various boards/platforms configs Kumar Gala
2005-06-02 23:29 ` Simon Richter
2005-06-03  8:01   ` Geert Uytterhoeven
2005-06-03 23:56     ` Benjamin Herrenschmidt
2005-06-06 15:11       ` [UPDATE] " Kumar Gala
2005-06-07  0:51         ` Allen Curtis
2005-06-07 21:47           ` Kumar Gala
2005-06-08  9:24             ` Gabriel Paubert
2005-06-08 14:36               ` Kumar Gala
2005-06-09 13:07             ` Kyle McMartin
2005-06-03  0:00 ` Mark A. Greer
2005-06-03  0:07   ` Benjamin Herrenschmidt
2005-06-03  0:09   ` Kumar Gala
2005-06-03  0:22     ` Benjamin Herrenschmidt
2005-06-03  5:41       ` Kumar Gala
2005-06-03  0:18 ` Matt Porter [this message]
2005-06-03  1:06   ` Dale Farnsworth
2005-06-03  6:40 ` Wojciech Kromer
2005-06-03 14:51 ` Pavel Fedin
2005-06-03  8:02   ` Geert Uytterhoeven
2005-06-03 23:56     ` Benjamin Herrenschmidt
  -- strict thread matches above, loose matches on Subject: below --
2005-06-03 18:43 Baxter, Robert
2005-06-08  4:42 ` Paul Mackerras
2005-06-08 13:45 Baxter, Robert

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=20050602171822.G24818@cox.net \
    --to=mporter@kernel$(echo .)crashing.org \
    --cc=kumar.gala@freescale$(echo .)com \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=linuxppc-embedded@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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