From: Franck Bui-Huu <vagabon.xyz@gmail.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: How to work with Linux-Mips ?
Date: Tue, 26 Sep 2006 09:14:07 +0200 [thread overview]
Message-ID: <4518D33F.9070208@innova-card.com> (raw)
Hi,
First of all, I'm sending this email because I really want to
understand how linux-mips is working with its community. I'm asking
this question because I'm wondering how many times I should resend a
patch before it can be considered for applying.
For example, I posted some patches more than one month ago. I really
think that these patches improve the MIPS specific code and they are
not complex at all:
http://www.linux-mips.org/archives/linux-mips/2006-08/msg00112.html
http://www.linux-mips.org/archives/linux-mips/2006-08/msg00113.html
http://www.linux-mips.org/archives/linux-mips/2006-08/msg00114.html
http://www.linux-mips.org/archives/linux-mips/2006-08/msg00115.html
http://www.linux-mips.org/archives/linux-mips/2006-08/msg00117.html
http://www.linux-mips.org/archives/linux-mips/2006-08/msg00118.html
http://www.linux-mips.org/archives/linux-mips/2006-08/msg00196.html
http://www.linux-mips.org/archives/linux-mips/2006-08/msg00195.html
http://www.linux-mips.org/archives/linux-mips/2006-08/msg00197.html
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.
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 ? 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 ?
Hoping this time I'll get some answers.
Franck
next reply other threads:[~2006-09-26 7:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 7:14 Franck Bui-Huu [this message]
2006-09-26 13:48 ` How to work with Linux-Mips ? 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
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=4518D33F.9070208@innova-card.com \
--to=vagabon.xyz@gmail.com \
--cc=linux-mips@linux-mips.org \
--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