From: Jakub Kicinski <kuba@kernel.org>
To: Yevhen Orlov <yevhen.orlov@plvision.eu>
Cc: netdev@vger.kernel.org,
Volodymyr Mytnyk <volodymyr.mytnyk@plvision.eu>,
Taras Chornyi <taras.chornyi@plvision.eu>,
Mickey Rachamim <mickeyr@marvell.com>,
Serhiy Pshyk <serhiy.pshyk@plvision.eu>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Andrew Lunn <andrew@lunn.ch>,
Stephen Hemminger <stephen@networkplumber.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v1 0/2] net: marvell: prestera: add ipv6 routes offloading
Date: Mon, 19 Dec 2022 17:46:03 -0800 [thread overview]
Message-ID: <20221219174603.39b4183c@kernel.org> (raw)
In-Reply-To: <Y5+RDIIGWGeKGUAo@yorlov.ow.s>
On Mon, 19 Dec 2022 00:15:40 +0200 Yevhen Orlov wrote:
> Add support for IPv6 nexthop/blackhole/connected routes for Marvell Prestera driver.
> Handle AF_INET6 neigbours, fib entries.
>
> Add features:
> - IPv6:
> - Support "offload", "offload_failed", "trap" flags
> - Support blackhole, nexthop, local/connected/unreachable/etc (trap)
> e.g.: "ip addr add 2001:1::1/64 dev sw1p2"
> e.g.: "ip route add 2002:2::/64 via 2001:2::2"
> e.g.: "ip route add blachole 2003:2::/64 dev lo"
# Form letter - net-next is closed
We have already submitted the networking pull request to Linus
for v6.2 and therefore net-next is closed for new drivers, features,
code refactoring and optimizations. We are currently accepting
bug fixes only.
Please repost when net-next reopens after Jan 2nd.
RFC patches sent for review only are obviously welcome at any time.
prev parent reply other threads:[~2022-12-20 1:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-18 22:15 [PATCH net-next v1 0/2] net: marvell: prestera: add ipv6 routes offloading Yevhen Orlov
2022-12-20 1:46 ` Jakub Kicinski [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=20221219174603.39b4183c@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mickeyr@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=serhiy.pshyk@plvision.eu \
--cc=stephen@networkplumber.org \
--cc=taras.chornyi@plvision.eu \
--cc=volodymyr.mytnyk@plvision.eu \
--cc=yevhen.orlov@plvision.eu \
/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).