From: Jon Maloy <jon.maloy@ericsson.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org,
Paul Gortmaker <paul.gortmaker@windriver.com>,
erik.hugne@ericsson.com, ying.xue@windriver.com,
maloy@donjonn.com, tipc-discussion@lists.sourceforge.net,
Jon Maloy <jon.maloy@ericsson.com>
Subject: [PATCH net-next 0/3] tipc: remove some unnecessary complexity
Date: Thu, 2 Apr 2015 09:32:59 -0400 [thread overview]
Message-ID: <1427981582-30819-1-git-send-email-jon.maloy@ericsson.com> (raw)
The TIPC code is unnecessarily complex in some places, often because
the conditions or assumptions that were the cause for the complexity
are not valid anymore.
In these three commits, we eliminate some cases of such redundant
complexity.
Jon Maloy (3):
tipc: drop tunneled packet duplicates at reception
tipc: eliminate delayed link deletion at link failover
tipc: simplify link mtu negotiation
net/tipc/bcast.c | 4 +-
net/tipc/link.c | 343 ++++++++++++++++++-------------------------------------
net/tipc/link.h | 29 +++--
net/tipc/msg.c | 4 +-
net/tipc/msg.h | 10 +-
net/tipc/node.c | 22 ++--
6 files changed, 147 insertions(+), 265 deletions(-)
--
1.9.1
next reply other threads:[~2015-04-02 13:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 13:32 Jon Maloy [this message]
2015-04-02 13:33 ` [PATCH net-next 1/3] tipc: drop tunneled packet duplicates at reception Jon Maloy
2015-04-02 13:33 ` [PATCH net-next 2/3] tipc: eliminate delayed link deletion at link failover Jon Maloy
2015-04-02 13:33 ` [PATCH net-next 3/3] tipc: simplify link mtu negotiation Jon Maloy
2015-04-02 20:27 ` [PATCH net-next 0/3] tipc: remove some unnecessary complexity 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=1427981582-30819-1-git-send-email-jon.maloy@ericsson.com \
--to=jon.maloy@ericsson.com \
--cc=davem@davemloft.net \
--cc=erik.hugne@ericsson.com \
--cc=maloy@donjonn.com \
--cc=netdev@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=ying.xue@windriver.com \
/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).