netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: allan.stephens@windriver.com
Cc: nhorman@tuxdriver.com, netdev@vger.kernel.org,
	jon.maloy@ericsson.com, tipc-discussion@lists.sourceforge.net,
	hady@cyberus.ca
Subject: Re: [PATCH]: tipc: Fix oops on send prior to entering networked mode
Date: Thu, 25 Feb 2010 07:13:53 -0800 (PST)	[thread overview]
Message-ID: <20100225.071353.10926250.davem@davemloft.net> (raw)
In-Reply-To: <29C1DC0826876849BDD9F1C67ABA2943070F1849@ala-mail09.corp.ad.wrs.com>

From: "Stephens, Allan" <allan.stephens@windriver.com>
Date: Thu, 25 Feb 2010 06:24:15 -0800

> Later, the company that employs me found it necessary to enhance TIPC
> with new capabilities which would be included in a couple of our
> operating systems (one of which is Linux-based).  To meet our schedule,
> it was necessary to make a large number of major changes to TIPC, and it
> was felt that submitting these relatively untested changes to mainstream
> Linux would be potentially destabilzing and therefore undesirable.

Things were going just fine until Ericsson farmed the TIPC stuff out
to you guys, really.

In fact, an incredible amount of effort was made by the Ericsson folks
to get the TIPC stack upstream in the first place.

And now you guys made all of that basically for naught by taking your
work downstream.

A healthy upstream project turned into a "business decision."

Thanks!

The fact is, you would have had LESS work to do if you have integrated
your work upstream as a rule.  Us upstream folks would have been
handling any and all networking API changes transparently for you.

And people who run automated tools to validate code and look for bugs
would have been fixing bugs in TIPC for you.

The list goes on an on.

But it doesn't make any "business sense" for you to work on your code
upstream so you didn't do it.

And now you want to suggest that we dump huge unreviewable chunks of
code into the tree, again because it's less work for _YOU_.

Thanks!

  parent reply	other threads:[~2010-02-25 15:13 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-19 19:40 [PATCH]: tipc: Fix oops on send prior to entering networked mode Neil Horman
2010-02-22 22:44 ` Stephens, Allan
2010-02-23  1:11   ` Neil Horman
2010-02-23 15:02     ` Stephens, Allan
2010-02-23 16:09       ` Neil Horman
2010-02-23 16:21         ` Stephens, Allan
2010-02-24 18:53           ` Neil Horman
2010-02-24 19:05             ` Stephens, Allan
2010-02-24 21:15               ` Neil Horman
2010-02-25  1:38                 ` David Miller
2010-02-25 14:24                   ` Stephens, Allan
2010-02-25 15:06                     ` David Miller
2010-02-25 16:24                       ` Stephens, Allan
2010-02-25 15:13                     ` David Miller [this message]
2010-02-25 15:23                     ` Neil Horman
2010-02-25 20:33                       ` Stephens, Allan
2010-02-25 21:14                         ` Neil Horman
2010-02-24 21:19               ` Neil Horman
2010-02-25  1:34               ` David Miller
2010-02-25  1:42                 ` Neil Horman
2010-03-02 18:33 ` [PATCH]: tipc: Fix oops on send prior to entering networked mode (v2) Neil Horman
2010-03-03 16:51   ` Stephens, Allan
2010-03-03 18:31     ` [PATCH]: tipc: Fix oops on send prior to entering networked mode (v3) Neil Horman
2010-03-04  8:40       ` David Miller
2010-03-08 20:19   ` [PATCH]: tipc: Fix oops on send prior to entering networked mode (v2) David Miller
2010-03-08 20:49     ` Neil Horman
2010-03-08 21:13     ` Neil Horman
2010-03-08 21:26       ` David Miller

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=20100225.071353.10926250.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=allan.stephens@windriver.com \
    --cc=hady@cyberus.ca \
    --cc=jon.maloy@ericsson.com \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=tipc-discussion@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).