All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: nhorman@tuxdriver.com
Cc: allan.stephens@windriver.com, netdev@vger.kernel.org,
	jon.maloy@ericsson.com, tipc-discussion@lists.sourceforge.net
Subject: Re: [PATCH]: tipc: Fix oops on send prior to entering networked mode
Date: Wed, 24 Feb 2010 17:38:11 -0800 (PST)	[thread overview]
Message-ID: <20100224.173811.264809559.davem@davemloft.net> (raw)
In-Reply-To: <20100224211507.GC15380@hmsreliant.think-freely.org>

From: Neil Horman <nhorman@tuxdriver.com>
Date: Wed, 24 Feb 2010 16:15:07 -0500

> Looking at the 1.7.6 tarball on sourceforge, its dated 10/10/2008,
> so you've basically got a 1.5 year lag between the development
> version and the commited version that distributions are using (and
> counting).  I'm sorry, I'm not trying to be crass about this, but
> its rather disconcerting to see that kind of discrepancy between the
> code development point and whats in net-next.  It implies that the
> only fix for a tipc problem is a wholesale upgrade of the tipc
> directory in the kernel (since it would seem the sourceforge tipc
> cvs tree has gone unused for a few years).

I'm extremely upset about this.

Especially given the fact that EVERY DAMN TIME there were TIPC
patches posted I applied EVERY DAMN ONE of them, and I did so
in an expediant manner.

So there is zero reason for the TIPC protocol development to not have
occured upstream.  I, in fact, facilitated things to work that way in
the smoothest way possible, if only the TIPC developers had obliged.

  reply	other threads:[~2010-02-25  1:37 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 [this message]
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
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=20100224.173811.264809559.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=allan.stephens@windriver.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.