From: Franck Bui-Huu <vagabon.xyz@gmail.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Franck Bui-Huu <vagabon.xyz@gmail.com>, linux-mips@linux-mips.org
Subject: Re: How to work with Linux-Mips ?
Date: Tue, 26 Sep 2006 16:43:55 +0200 [thread overview]
Message-ID: <45193CAB.7040103@innova-card.com> (raw)
In-Reply-To: <20060926134848.GB27446@linux-mips.org>
Hi Ralf,
I'm glad you answered...
Ralf Baechle wrote:
> On Tue, Sep 26, 2006 at 09:14:07AM +0200, Franck Bui-Huu wrote:
>
>> 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...
>
> You should interpret a non-answer as exactly this.
>
Well, I usually do this interpretation at first but the patches were
posted more than one month ago and during this while you considered,
reviewed and applied several other patches.
Futhermore replying with a short email saying that you're _very_ busy
and you'll deal with them after 2.6.18 releasing would have been
welcome. And it would have taken less than 1 minute of your time.
>> 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 ?
>
> You should draw a line between linux-mips.org and MIPS Technologies.
> linux-mips.org isn't a formal organization and not to be considered part
> of MTI. If anything call it a loosely knit group of hackers with
> interest in running Linux and anything and all that has a MIPS processors.
Thanks for this clarification, which is a bit scaring, I wasn't aware
of this.
> There is more to be said I guess you rather want me to return to my
> pending patches ;-)
>
yes please go ahead. Just note that this email is not an attack or
whatever, I'm just trying to understand what I'm doing wrong.
Franck
next prev parent reply other threads:[~2006-09-26 14:43 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 [this message]
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=45193CAB.7040103@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