netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: linux-can@vger.kernel.org, davem@davemloft.net
Cc: Oliver Hartkopp <socketcan@hartkopp.net>,
	mkl@pengutronix.de, dev@kicherer.org, netdev@vger.kernel.org
Subject: [PATCH 2/8] can: remove obsolete pernet_operations definitions
Date: Tue, 25 Apr 2017 08:19:39 +0200	[thread overview]
Message-ID: <20170425061945.28722-3-socketcan@hartkopp.net> (raw)
In-Reply-To: <20170425061945.28722-1-socketcan@hartkopp.net>

The namespace support for the CAN subsystem does not need any additional
memory. So when ".size = 0" there's no extra memory allocated by the system.
And therefore ".id" is obsolete too.

Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net>
---
 net/can/af_can.c | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/net/can/af_can.c b/net/can/af_can.c
index 2c935babe466..421b60fc42c3 100644
--- a/net/can/af_can.c
+++ b/net/can/af_can.c
@@ -75,8 +75,6 @@ static int stats_timer __read_mostly = 1;
 module_param(stats_timer, int, S_IRUGO);
 MODULE_PARM_DESC(stats_timer, "enable timer for statistics (default:on)");
 
-static int can_net_id;
-
 static struct kmem_cache *rcv_cache __read_mostly;
 
 /* table of registered CAN protocols */
@@ -935,8 +933,6 @@ static struct notifier_block can_netdev_notifier __read_mostly = {
 static struct pernet_operations can_pernet_ops __read_mostly = {
 	.init = can_pernet_init,
 	.exit = can_pernet_exit,
-	.id = &can_net_id,
-	.size = 0,
 };
 
 static __init int can_init(void)
-- 
2.11.0


  parent reply	other threads:[~2017-04-25  6:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-25  6:19 [PATCH 0/8] Fix and complete CAN namespace support Oliver Hartkopp
2017-04-25  6:19 ` [PATCH 1/8] can: fix memory leak in initial " Oliver Hartkopp
2017-04-25  6:19 ` Oliver Hartkopp [this message]
2017-04-25  6:19 ` [PATCH 3/8] can: remove obsolete definitions Oliver Hartkopp
2017-04-25  6:19 ` [PATCH 4/8] can: complete initial namespace support Oliver Hartkopp
2017-04-25  6:19 ` [PATCH 5/8] can: network namespace support for CAN_BCM protocol Oliver Hartkopp
2017-04-25  6:19 ` [PATCH 6/8] can: network namespace support for CAN gateway Oliver Hartkopp
2017-04-25  6:19 ` [PATCH 7/8] can: add Virtual CAN Tunnel driver (vxcan) Oliver Hartkopp
2017-04-25  6:19 ` [PATCH 8/8] can: enable module auto loading for virtual CAN interfaces Oliver Hartkopp
2017-04-25  6:48 ` [PATCH 0/8] Fix and complete CAN namespace support Marc Kleine-Budde
2017-04-25  8:43   ` Oliver Hartkopp
2017-04-25  8:45   ` Marc Kleine-Budde
2017-04-25  8:48     ` Oliver Hartkopp
2017-04-25  8:49       ` Marc Kleine-Budde

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=20170425061945.28722-3-socketcan@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=davem@davemloft.net \
    --cc=dev@kicherer.org \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.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).