From: David Miller <davem@davemloft.net>
To: jiri@resnulli.us
Cc: netdev@vger.kernel.org, idosch@mellanox.com, eladr@mellanox.com,
yotamg@mellanox.com, nogahf@mellanox.com, ogerlitz@mellanox.com
Subject: Re: [patch net v2 0/2] mlxsw: Couple of router fixes
Date: Thu, 10 Nov 2016 13:02:51 -0500 (EST) [thread overview]
Message-ID: <20161110.130251.1602510155269331989.davem@davemloft.net> (raw)
In-Reply-To: <1478777465-6567-1-git-send-email-jiri@resnulli.us>
From: Jiri Pirko <jiri@resnulli.us>
Date: Thu, 10 Nov 2016 12:31:03 +0100
> From: Jiri Pirko <jiri@mellanox.com>
>
> ---
> v1->v2:
> - patch2:
> - use net_eq
Series applied, thanks Jiri.
prev parent reply other threads:[~2016-11-10 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 11:31 [patch net v2 0/2] mlxsw: Couple of router fixes Jiri Pirko
2016-11-10 11:31 ` [patch net v2 1/2] mlxsw: spectrum_router: Fix handling of neighbour structure Jiri Pirko
2016-11-10 11:31 ` [patch net v2 2/2] mlxsw: spectrum_router: Ignore FIB notification events for non-init namespaces Jiri Pirko
2016-11-10 18:02 ` David Miller [this message]
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=20161110.130251.1602510155269331989.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eladr@mellanox.com \
--cc=idosch@mellanox.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=nogahf@mellanox.com \
--cc=ogerlitz@mellanox.com \
--cc=yotamg@mellanox.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;
as well as URLs for NNTP newsgroup(s).