From: David Miller <davem@davemloft.net>
To: jon.maloy@ericsson.com
Cc: netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net,
mohan.krishna.ghanta.krishnamurthy@ericsson.com
Subject: Re: [net-next 0/5] tipc: obsolete zone concept
Date: Sat, 17 Mar 2018 17:12:02 -0400 (EDT) [thread overview]
Message-ID: <20180317.171202.1076871106467200093.davem@davemloft.net> (raw)
In-Reply-To: <1521128935-6141-1-git-send-email-jon.maloy@ericsson.com>
From: Jon Maloy <jon.maloy@ericsson.com>
Date: Thu, 15 Mar 2018 16:48:49 +0100
> Functionality related to the 'zone' concept was never implemented in
> TIPC. In this series we eliminate the remaining traces of it in the
> code, and can hence take a first step in reducing the footprint and
> complexity of the binding table.
Series applied, thanks Jon.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
prev parent reply other threads:[~2018-03-17 21:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 15:48 [net-next 0/5] tipc: obsolete zone concept Jon Maloy
2018-03-15 15:48 ` Jon Maloy
2018-03-15 15:48 ` [net-next 1/5] tipc: obsolete TIPC_ZONE_SCOPE Jon Maloy
2018-03-15 16:11 ` Jiri Pirko
2018-03-15 16:27 ` Jon Maloy
2018-03-15 16:37 ` Jiri Pirko
2018-03-15 15:48 ` [net-next 2/5] tipc: remove zone publication list in name table Jon Maloy
2018-03-15 15:48 ` [net-next 3/5] tipc: remove zone_list member in struct publication Jon Maloy
2018-03-15 15:48 ` [net-next 4/5] tipc: merge two lists " Jon Maloy
2018-03-15 15:48 ` [net-next 5/5] tipc: some name changes Jon Maloy
2018-03-17 21:12 ` David Miller [this message]
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=20180317.171202.1076871106467200093.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jon.maloy@ericsson.com \
--cc=mohan.krishna.ghanta.krishnamurthy@ericsson.com \
--cc=netdev@vger.kernel.org \
--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).