From: David Ahern <dsahern@gmail.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
David Miller <davem@davemloft.net>
Cc: David Ahern <dsahern@kernel.org>,
Network Development <netdev@vger.kernel.org>,
Ido Schimmel <idosch@mellanox.com>,
Saeed Mahameed <saeedm@mellanox.com>,
Martin KaFai Lau <kafai@fb.com>, Wei Wang <weiwan@google.com>
Subject: Re: [PATCH v3 net-next 0/7] net: add struct nexthop to fib{6}_info
Date: Tue, 4 Jun 2019 21:05:20 -0600 [thread overview]
Message-ID: <8f0805f3-f240-9a94-5faf-3141bd74a433@gmail.com> (raw)
In-Reply-To: <CAADnVQLRjBQaoYA0Af12dBLgzWqFjOmpnY+kBrhQNrpQQqQEsg@mail.gmail.com>
On 6/4/19 9:03 PM, Alexei Starovoitov wrote:
> As far as I can see the discussion on a better path forward
> was still ongoing in v2 thread between David, Martin and Wei.
> Since the set is already applied it demotivated everyone
> to review and discuss it further.
> Please reconsider such decisions in the future.
The discussion on the other thread has nothing to do with this patch
set; it is about changing / removing *existing* code.
prev parent reply other threads:[~2019-06-05 3:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 3:19 [PATCH v3 net-next 0/7] net: add struct nexthop to fib{6}_info David Ahern
2019-06-04 3:19 ` [PATCH v3 net-next 1/7] ipv4: Use accessors for fib_info nexthop data David Ahern
2019-06-04 3:19 ` [PATCH v3 net-next 2/7] ipv4: Prepare for fib6_nh from a nexthop object David Ahern
2019-06-04 3:19 ` [PATCH v3 net-next 3/7] ipv4: Plumb support for nexthop object in a fib_info David Ahern
2019-06-04 3:19 ` [PATCH v3 net-next 4/7] ipv6: Plumb support for nexthop object in a fib6_info David Ahern
2019-06-04 3:19 ` [PATCH v3 net-next 5/7] mlxsw: Fail attempts to use routes with nexthop objects David Ahern
2019-06-04 3:19 ` [PATCH v3 net-next 6/7] mlx5: " David Ahern
2019-06-04 3:19 ` [PATCH v3 net-next 7/7] rocker: " David Ahern
2019-06-05 2:27 ` [PATCH v3 net-next 0/7] net: add struct nexthop to fib{6}_info David Miller
2019-06-05 3:03 ` Alexei Starovoitov
2019-06-05 3:05 ` David Ahern [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=8f0805f3-f240-9a94-5faf-3141bd74a433@gmail.com \
--to=dsahern@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=idosch@mellanox.com \
--cc=kafai@fb.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.com \
--cc=weiwan@google.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.