From: Franck Bui-Huu <vagabon.xyz@gmail.com>
To: Peter Popov <ppopov@embeddedalley.com>
Cc: Franck <vagabon.xyz@gmail.com>,
Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org
Subject: Re: How to work with Linux-Mips ?
Date: Thu, 28 Sep 2006 09:42:03 +0200 [thread overview]
Message-ID: <451B7CCB.1060406@innova-card.com> (raw)
In-Reply-To: <4519859A.1090306@embeddedalley.com>
Peter Popov wrote:
> <snip>
>
>
>> These patchs have been kindly reviewed and acked by Atsushi Nemoto,
>> but then no feedback from the MIPS team. I tried to get a status for
>> MIPS team a couple of time, to know if something was wrong with them
>> but MIPS people seem to not care about them. They even haven't
>> bothered to take 10 seconds for replying something like:
>
>
>> - your patches are broken because...
>>
>> - your patches do not respect our MIPS protocol, please resend...
>>
>> - Sorry we are very busy, please hold on...
>>
>> - OK your patches suck please try to work on ARM chips because MIPS
>> is a very closed circle reserved to MIPS gurus.
>
> There is no such thing as a 10 sec patch review. Especially when it
> comes to patches that touch generic portions of the kernel. Someone has
> to very carefully consider what they are doing, any potential risks, how
Who is claiming that ? I've never said that patch review needs 10 sec to
be done....
>
> MIPS Tech and linux-mips are separate entities. Personally I think MIPS
> Tech has done a great service to themselves, their customers, and the
> entire Linux MIPS community, by hiring Ralf to do new MIPS development
> and properly support new chips coming out.
Again, none has said the contrary...
Franck
prev parent reply other threads:[~2006-09-28 7:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 7:14 How to work with Linux-Mips ? Franck Bui-Huu
2006-09-26 13:48 ` Ralf Baechle
2006-09-26 14:43 ` Franck Bui-Huu
2006-09-26 19:55 ` Peter Popov
2006-09-27 3:18 ` Jonathan Day
2006-09-28 8:45 ` Franck Bui-Huu
2006-09-28 7:42 ` Franck Bui-Huu [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=451B7CCB.1060406@innova-card.com \
--to=vagabon.xyz@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=ppopov@embeddedalley.com \
--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