From: David Miller <davem@redhat.com>
To: callum.sinclair@alliedtelesis.co.nz
Cc: kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org,
nikolay@cumulusnetworks.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ipmr: ip6mr: Create new sockopt to clear mfc cache only
Date: Sat, 02 Feb 2019 19:42:24 -0800 (PST) [thread overview]
Message-ID: <20190202.194224.82433482865207218.davem@redhat.com> (raw)
In-Reply-To: <20190130205209.18183-2-callum.sinclair@alliedtelesis.co.nz>
From: Callum Sinclair <callum.sinclair@alliedtelesis.co.nz>
Date: Thu, 31 Jan 2019 09:52:09 +1300
>
> -/* Close the multicast socket, and clear the vif tables etc */
> -static void mroute_clean_tables(struct mr_table *mrt, bool all)
> +/* Clear the vif tables */
> +static void mroute_clean_cache(struct mr_table *mrt, bool all)
> {
> - struct net *net = read_pnet(&mrt->net);
> struct mr_mfc *c, *tmp;
> struct mfc_cache *cache;
> - LIST_HEAD(list);
> - int i;
> -
> - /* Shut down all active vif entries */
> - for (i = 0; i < mrt->maxvif; i++) {
> - if (!all && (mrt->vif_table[i].flags & VIFF_STATIC))
> - continue;
> - vif_delete(mrt, i, 0, &list);
> - }
> - unregister_netdevice_many(&list);
> + struct net *net = read_pnet(&mrt->net);
Please do not change the order of local variables like this, you're breaking
the correct reverse christmas tree ordering of longest to shortest line for
local variable declarations.
Thanks.
next prev parent reply other threads:[~2019-02-03 3:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 20:52 [PATCH] ipmr: ip6mr: Create new sockopt to clear mfc cache only Callum Sinclair
2019-01-30 20:52 ` Callum Sinclair
2019-02-03 3:42 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-07 2:08 Callum Sinclair
2019-02-07 2:08 ` [PATCH] " Callum Sinclair
2019-02-07 6:32 ` Nikolay Aleksandrov
2019-02-05 2:57 Callum Sinclair
2019-02-05 2:58 ` Callum Sinclair
2019-02-05 19:52 ` Nikolay Aleksandrov
2019-01-30 2:25 Callum Sinclair
2019-01-30 2:25 ` Callum Sinclair
2019-01-30 5:42 ` kbuild test robot
2019-01-30 7:13 ` kbuild test robot
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=20190202.194224.82433482865207218.davem@redhat.com \
--to=davem@redhat.com \
--cc=callum.sinclair@alliedtelesis.co.nz \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=yoshfuji@linux-ipv6.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).