From: Jiri Pirko <jiri@resnulli.us>
To: Jon Maloy <jon.maloy@ericsson.com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Mohan Krishna Ghanta Krishnamurthy
<mohan.krishna.ghanta.krishnamurthy@ericsson.com>,
Tung Quang Nguyen <tung.q.nguyen@dektech.com.au>,
Hoang Huu Le <hoang.h.le@dektech.com.au>,
Canh Duc Luu <canh.d.luu@dektech.com.au>,
Ying Xue <ying.xue@windriver.com>,
"tipc-discussion@lists.sourceforge.net"
<tipc-discussion@lists.sourceforge.net>
Subject: Re: [net-next 1/5] tipc: obsolete TIPC_ZONE_SCOPE
Date: Thu, 15 Mar 2018 17:37:08 +0100 [thread overview]
Message-ID: <20180315163708.GI2130@nanopsycho> (raw)
In-Reply-To: <DM5PR15MB15620DD9157E5EAECB63941E9AD00@DM5PR15MB1562.namprd15.prod.outlook.com>
Thu, Mar 15, 2018 at 05:27:17PM CET, jon.maloy@ericsson.com wrote:
>No, it won't. I just moved those functions and #defines to the bottom of the same file, and marked them as 'deprecated'.
Ah. That I missed. Thanks!
next prev parent reply other threads:[~2018-03-15 16:37 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 [this message]
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 ` [net-next 0/5] tipc: obsolete zone concept 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=20180315163708.GI2130@nanopsycho \
--to=jiri@resnulli.us \
--cc=canh.d.luu@dektech.com.au \
--cc=davem@davemloft.net \
--cc=hoang.h.le@dektech.com.au \
--cc=jon.maloy@ericsson.com \
--cc=mohan.krishna.ghanta.krishnamurthy@ericsson.com \
--cc=netdev@vger.kernel.org \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=tung.q.nguyen@dektech.com.au \
--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