From: Ben Warren <bwarren@qstreams.com>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: D'Abbraccio Joe-ljd015 <Joe.D'abbraccio@freescale.com>,
linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] Add platform support for the MPC837x RDB board
Date: Mon, 01 Oct 2007 15:49:22 -0400 [thread overview]
Message-ID: <47014F42.1010106@qstreams.com> (raw)
In-Reply-To: <20071001191937.GA5785@mag.az.mvista.com>
Mark A. Greer wrote:
> On Thu, Sep 27, 2007 at 04:28:30PM -0500, Olof Johansson wrote:
>
>> On Thu, Sep 27, 2007 at 03:03:12PM -0500, Josh Boyer wrote:
>>
>>> On Thu, 27 Sep 2007 12:53:51 -0700
>>> "Mark A. Greer" <mgreer@mvista.com> wrote:
>>>
>>>
>>>> On Thu, Sep 27, 2007 at 12:41:57PM -0700, D'Abbraccio Joe-ljd015 wrote:
>>>>
>>>>> Thanks for the advice, but I was just basing the list to post to on the
>>>>> MAINTAINERS file which states that this is the one for Embedded PPC83XX.
>>>>> If you still think that I should post to linuxppc-dev, let me know.
>>>>>
>>>> Yes, I think it would be better to repost to linuxppc-dev.
>>>>
>>>> Does anyone have an objection to changing all of the:
>>>>
>>>> "L: linuxppc-embedded@ozlabs.org"
>>>>
>>>> in MAINTAINERS to:
>>>>
>>>> "L: linuxppc-dev@ozlabs.org" ??
>>>>
>>>> Kumar, Josh, Vitaly, et. al.?
>>>>
>>> I personally don't care either way. I'm already subscribed to both
>>> lists.
>>>
>>> Makes sense to go to linuxppc-dev given the arch/powerpc migration.
>>>
>> I thought the -embedded list was created in the first place to keep some
>> of the "noise" off of -dev (i.e. "I can't get interface <foo> to work on
>> my custom <embedded eval board>-lookalike board, HELP!"). If people still
>> care about keeping that on a separate list, then we shouldn't change it.
>>
>
> Yes, IIRC, that was the reason but now with the merge and low volume on this
> list, it makes sense to me to just get rid of -embedded.
>
>
Perhaps my perspective is unique, but I doubt it. I find it nice that
this list is low volume and not filled with endless patches about CHRP
and P series and open firmware syntax blah blah blah...
No offense intended to all the people who are doing wonderful work
expanding the Linux universe, but for your average dude or dudette
working on embedded boards that happen to have a PowerPC processor, this
list is a pretty good forum.
regards,
Ben
next prev parent reply other threads:[~2007-10-01 19:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 18:22 [PATCH] Add platform support for the MPC837x RDB board ljd015
2007-09-27 19:10 ` Mark A. Greer
2007-09-27 19:41 ` D'Abbraccio Joe-ljd015
2007-09-27 19:53 ` Mark A. Greer
2007-09-27 20:03 ` Josh Boyer
2007-09-27 21:28 ` Olof Johansson
2007-10-01 19:19 ` Mark A. Greer
2007-10-01 19:49 ` Ben Warren [this message]
2007-10-01 19:59 ` Josh Boyer
2007-10-01 20:07 ` Ben Warren
2007-10-01 20:10 ` Mark A. Greer
2007-09-27 21:31 ` Kumar Gala
2007-09-27 21:40 ` Kumar Gala
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=47014F42.1010106@qstreams.com \
--to=bwarren@qstreams.com \
--cc=Joe.D'abbraccio@freescale.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=mgreer@mvista.com \
/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