> 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
to test them, etc. Multiply that times the number of people sending
patches plus the new development that someone like Ralf is doing. Try
working full time and being a maintainer yourself for a single board
only over a period of a few years.
> Another question, is that MIPS tree seems to not care about linux
> mainline release process. I actually notice that even Linus do not
> pull MIPS tree anymore during the last release candidate cycle. Is
> MIPS aware that some of its customers are trying to make stable
> releases ?
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.
> Does the linux-mips team exist to ease life of its
> customers to use the linux kernel on MIPS chips or is the purpose of
> this team doing only some development for fun ?
Does it really matter? The developers that are active on the linux-mips
mailing list are not associated with MIPS Tech nor are they paid for
their effort by you or the company you work for. If you want a
"product", you can buy a commercial embedded Linux distro from someone.
If you want to contribute to the linux mips development effort, then
learn to live with any frustrations associated with working in community
trees. And next time, just ask nicely what you can do to get some
feedback on your patches.