From: Wojciech Kromer <wojciech.kromer@dgt•com.pl>
To: undisclosed-recipients: ;
Subject: [Fwd: Re: Getting ownership for various boards/platforms configs]
Date: Mon, 06 Jun 2005 08:09:04 +0200 [thread overview]
Message-ID: <42A3E880.6030309@dgt.com.pl> (raw)
[-- Attachment #1: Type: text/plain, Size: 1 bytes --]
[-- Attachment #2: Re: Getting ownership for various boards/platforms configs --]
[-- Type: message/rfc822, Size: 2896 bytes --]
From: Allen Curtis <acurtis@onz•com>
To: Wojciech Kromer <wojciech.kromer@dgt•com.pl>
Subject: Re: Getting ownership for various boards/platforms configs
Date: Fri, 3 Jun 2005 07:27:41 -0700
Message-ID: <efe74c750b938026bd9564214c19a598@onz•com>
If you are looking for maintainers, I will work on the PPC stuff. The
#ifdef situation has been out of control for quite some time. I did
attempt to consolidate the platform stuff. Some of this work did make
it into the kernel. Are you talking about 2.6? I was about to work on
the sysfs stuff which will go a long way to cleaning up the device
drivers.
BTW: the linuxppc-embedded list did not show in the reply list. Forward
this if you want.
>> 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.
>>
>>
> There is another issue..
>
> May I suggest to add one full-custom board?
> There are a lot of changes to do inside uart,fec,fcc drivers with a lot
> of #ifdefs,
> just because different use of mpc resources on different boards.
> Why it's not configured via menuconfig?
> Another nice example is inside status_led.h...
reply other threads:[~2005-06-06 6:08 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=42A3E880.6030309@dgt.com.pl \
--to=wojciech.kromer@dgt$(echo .)com.pl \
/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