DPDK patches and discussions
 help / color / mirror / Atom feed
From: Vincent Guo <guopengfei160@163.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v2] kni: Bug fix in module_init and module_exit
Date: Fri,  2 Sep 2016 18:23:13 +0800	[thread overview]
Message-ID: <1472811793-4433-1-git-send-email-guopengfei160@163.com> (raw)
In-Reply-To: <1472436734-5538-1-git-send-email-guopengfei160@163.com>

Fix pernet calls when HAVE_SIMPLIFIED_PERNET_OPERATIONS is not set.

Fixes: e6734d21b4e1 ("kni: fix build with kernel 2.6.32")

Signed-off-by: Vincent Guo <guopengfei160@163.com>
---
 lib/librte_eal/linuxapp/kni/kni_misc.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/lib/librte_eal/linuxapp/kni/kni_misc.c b/lib/librte_eal/linuxapp/kni/kni_misc.c
index 67e9b7d..d7850be 100644
--- a/lib/librte_eal/linuxapp/kni/kni_misc.c
+++ b/lib/librte_eal/linuxapp/kni/kni_misc.c
@@ -194,7 +194,7 @@ out:
 #ifdef HAVE_SIMPLIFIED_PERNET_OPERATIONS
 	unregister_pernet_subsys(&kni_net_ops);
 #else
-	register_pernet_gen_subsys(&kni_net_id, &kni_net_ops);
+	unregister_pernet_gen_subsys(kni_net_id, &kni_net_ops);
 #endif
 	return rc;
 }
@@ -206,7 +206,7 @@ kni_exit(void)
 #ifdef HAVE_SIMPLIFIED_PERNET_OPERATIONS
 	unregister_pernet_subsys(&kni_net_ops);
 #else
-	register_pernet_gen_subsys(&kni_net_id, &kni_net_ops);
+	unregister_pernet_gen_subsys(kni_net_id, &kni_net_ops);
 #endif
 	KNI_PRINT("####### DPDK kni module unloaded  #######\n");
 }
-- 
2.4.0

  parent reply	other threads:[~2016-09-02 10:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-29  2:12 [dpdk-dev] [PATCH] " Vincent Guo
2016-08-29  9:36 ` Ferruh Yigit
2016-08-29  9:38   ` Ferruh Yigit
2016-09-02 10:23 ` Vincent Guo [this message]
2016-09-06  8:02   ` [dpdk-dev] [PATCH v2] kni: " Ferruh Yigit
2016-09-09 14:31     ` Thomas Monjalon

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=1472811793-4433-1-git-send-email-guopengfei160@163.com \
    --to=guopengfei160@163.com \
    --cc=dev@dpdk.org \
    /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).