From: David Ahern <dsa@cumulusnetworks.com>
To: Nikolay Aleksandrov <razor@blackwall.org>, netdev@vger.kernel.org
Cc: shm@cumulusnetworks.com, davem@davemloft.net,
Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Subject: Re: [PATCH net-next 0/4] vrf: a few simplifications and cleanups
Date: Tue, 18 Aug 2015 13:38:23 -0600 [thread overview]
Message-ID: <55D389AF.1010403@cumulusnetworks.com> (raw)
In-Reply-To: <1439918884-13681-1-git-send-email-razor@blackwall.org>
On 8/18/15 11:28 AM, Nikolay Aleksandrov wrote:
> From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
>
> Hi,
> These patches remove some unnecessary checks (patches 3, 4), unnecessary
> num_slaves member and refcnt manipulations which are already done by the
> upper functions.
>
> Cheers,
> Nik
>
> Nikolay Aleksandrov (4):
> vrf: drop unnecessary dev refcnt changes
> vrf: drop unused num_slaves member
> vrf: don't check for dstats and rth in uninit path
> vrf: simplify the netdev notifier function
>
> drivers/net/vrf.c | 15 ++++-----------
> include/net/vrf.h | 1 -
> 2 files changed, 4 insertions(+), 12 deletions(-)
>
Looks good to me. Thanks, Nikolay.
Acked-by: David Ahern <dsa@cumulusnetworks.com>
next prev parent reply other threads:[~2015-08-18 19:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 17:28 [PATCH net-next 0/4] vrf: a few simplifications and cleanups Nikolay Aleksandrov
2015-08-18 17:28 ` [PATCH net-next 1/4] vrf: drop unnecessary dev refcnt changes Nikolay Aleksandrov
2015-08-18 17:28 ` [PATCH net-next 2/4] vrf: drop unused num_slaves member Nikolay Aleksandrov
2015-08-18 17:28 ` [PATCH net-next 3/4] vrf: don't check for dstats and rth in uninit path Nikolay Aleksandrov
2015-08-18 17:28 ` [PATCH net-next 4/4] vrf: simplify the netdev notifier function Nikolay Aleksandrov
2015-08-18 19:38 ` David Ahern [this message]
2015-08-19 3:17 ` [PATCH net-next 0/4] vrf: a few simplifications and cleanups 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=55D389AF.1010403@cumulusnetworks.com \
--to=dsa@cumulusnetworks.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=razor@blackwall.org \
--cc=shm@cumulusnetworks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.