From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: David Ahern <dsahern@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Michael Jeanson <mjeanson@efficios.com>,
David Ahern <dsahern@kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] selftests: Add VRF icmp error route lookup test
Date: Tue, 11 Aug 2020 15:27:41 -0400 (EDT) [thread overview]
Message-ID: <731739593.4827.1597174061640.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <511074db-a005-9b64-9b5a-6367d1ac0af6@gmail.com>
----- On Aug 11, 2020, at 3:14 PM, David Ahern dsahern@gmail.com wrote:
> On 8/11/20 1:11 PM, Mathieu Desnoyers wrote:
>> One thing I am missing before this series can be considered for upstreaming
>> is an Acked-by of the 2 fixes for ipv4 and ipv6 from you, as maintainer
>> of l3mdev, if you think the approach I am taking with those fixes makes sense.
>
> Send the set, and I will review as vrf/l3mdev maintainer. I need working
> tests and patches to see the before and after.
Allright, I'm rebasing on the net tree as we speak, and the patches will
be on their way shortly.
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
prev parent reply other threads:[~2020-08-11 19:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 21:12 [RFC PATCH 1/3] selftests: Add VRF icmp error route lookup test Mathieu Desnoyers
2020-07-29 21:12 ` [RFC PATCH 2/3] ipv4/icmp: l3mdev: Perform icmp error route lookup on source device routing table Mathieu Desnoyers
2020-07-29 21:12 ` [RFC PATCH 3/3] ipv6/icmp: " Mathieu Desnoyers
2020-08-06 17:00 ` [RFC PATCH 1/3] selftests: Add VRF icmp error route lookup test David Ahern
2020-08-06 18:51 ` [PATCH] " Michael Jeanson
2020-08-11 17:28 ` David Miller
2020-08-11 18:57 ` David Ahern
2020-08-11 19:11 ` Mathieu Desnoyers
2020-08-11 19:14 ` David Ahern
2020-08-11 19:27 ` Mathieu Desnoyers [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=731739593.4827.1597174061640.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=dsahern@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjeanson@efficios.com \
--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 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.