From: "E-Blokos" <infos@e-blokos.com>
To: <linux-rt-users@vger.kernel.org>
Subject: Re: Plan to support RT on 3.8
Date: Fri, 18 Jan 2013 19:04:25 -0500 [thread overview]
Message-ID: <66EBDBF9E9BE41EDB669191411467716@e1705> (raw)
In-Reply-To: alpine.LFD.2.02.1301181904470.2935@ionos
----- Original Message -----
From: "Thomas Gleixner" <tglx@linutronix.de>
To: "Jain Priyanka-B32167" <B32167@freescale.com>
Cc: "Carsten Emde" <C.Emde@osadl.org>; "Steven Rostedt"
<rostedt@goodmis.org>; <linux-rt-users@vger.kernel.org>; "Dev Manish-R65866"
<R65866@freescale.com>
Sent: Friday, January 18, 2013 5:55 PM
Subject: Re: Plan to support RT on 3.8
> Jain,
>
> please do not take this reply as a personal affront!
>
> This is solely about the impertinence of your employer as I have
> already ignored _three_ private mails with the same topic originated
> from Freescale management folks.
>
> Though, I'm happy that you've been obviously forced by the same people
> which I ignored to send this mail. Otherwise I wouldn't have been able
> to give a public response.
>
> On Fri, 18 Jan 2013, Jain Priyanka-B32167 wrote:
>
>> We are planning for our next BSP. For that. We would like to use
>> Linux kernel 3.8.
>>
>> It would be really helpful if you can please share the plan of RT
>> support on 3.8 kernel.
>>
>> When can the release be expected?
>
> I think I've made it entirely clear in the past, that these stupid
> roadmap and release plan questions are annoying as hell.
>
> See: http://bit.ly/XJF0em
>
> I'm really amazed by the chuzpa of Freescale management folks to
> demand information from an Open Source project solely for the sake of
> Freescale business decisions.
>
> I would not mind such a demand from someone who actively fosters the
> development of this project (either by providing substantial man power
> or by sustainably funding it), but it seems that none of the managers
> at Freescale noticed my recent observations about participation on
> PREEMPT_RT.
>
> See: https://lwn.net/Articles/524329/
> and https://lwn.net/Articles/232379/
>
>
> Just to make it clear:
>
> - Neither I nor anyone else in the PREEMPT_RT community has any
> interest in Freescale business decisions.
>
> - I personally detest the abuse of Freescale engineers who are
> involved with this project to be forced to gain information which
> their managers could not get.
>
> - I call out Freescale management folks to explain why they think
> that Open Source free-riding entitles them to demand anything from
> the community.
>
> Thanks,
>
> tglx
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rt-users"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
Why Freescale corporation didn'et make any donation to RT open source
project already
if they need RT super developers ? :o)
Seems that human nature wants always pervert freedom for their profits....
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
next prev parent reply other threads:[~2013-01-19 0:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AC83832D6324604BB08FAE5A33553F190B24DB89@039-SN2MPN1-011.039d.mgd.msft.net>
2013-01-18 22:55 ` Plan to support RT on 3.8 Thomas Gleixner
2013-01-19 0:04 ` E-Blokos [this message]
2013-01-20 8:43 ` Jain Priyanka-B32167
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=66EBDBF9E9BE41EDB669191411467716@e1705 \
--to=infos@e-blokos.com \
--cc=linux-rt-users@vger.kernel.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