From: Steffen Klassert <steffen.klassert@secunet.com>
To: Florian Westphal <fw@strlen.de>
Cc: <netdev@vger.kernel.org>, <herbert@gondor.apana.org.au>
Subject: Re: [PATCH ipsec-next v2 0/5] xfrm: ipv6: remove hdr_off indirection
Date: Mon, 14 Jun 2021 11:55:07 +0200 [thread overview]
Message-ID: <20210614095507.GV40979@gauss3.secunet.de> (raw)
In-Reply-To: <20210611105014.4675-1-fw@strlen.de>
On Fri, Jun 11, 2021 at 12:50:09PM +0200, Florian Westphal wrote:
> v2: fix build failure with MIP6=y in last patch.
>
> IPV6 xfrm moves mutable extension headers to make space for the
> encapsulation header.
>
> For Mobile ipv6 sake this uses an indirect call (ipv6 can be built
> as module).
>
> These patches remove those indirections by placing a
> small parsing function in the xfrm core.
>
> While at it, the merged dstopt/rt hdroff function is
> realigned with ip6_find_1stfragopt (where they were copied from).
>
> ip6_find_1stfragopt received bug fixes that were missing from the
> cloned ones.
>
> Florian Westphal (5):
> xfrm: ipv6: add xfrm6_hdr_offset helper
> xfrm: ipv6: move mip6_destopt_offset into xfrm core
> xfrm: ipv6: move mip6_rthdr_offset into xfrm core
> xfrm: remove hdr_offset indirection
> xfrm: merge dstopt and routing hdroff functions
Series applied, thanks Florian!
prev parent reply other threads:[~2021-06-14 9:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 10:50 [PATCH ipsec-next v2 0/5] xfrm: ipv6: remove hdr_off indirection Florian Westphal
2021-06-11 10:50 ` [PATCH ipsec-next v2 1/5] xfrm: ipv6: add xfrm6_hdr_offset helper Florian Westphal
2021-06-11 10:50 ` [PATCH ipsec-next v2 2/5] xfrm: ipv6: move mip6_destopt_offset into xfrm core Florian Westphal
2021-06-11 10:50 ` [PATCH ipsec-next v2 3/5] xfrm: ipv6: move mip6_rthdr_offset " Florian Westphal
2021-06-11 10:50 ` [PATCH ipsec-next v2 4/5] xfrm: remove hdr_offset indirection Florian Westphal
2021-06-11 10:50 ` [PATCH ipsec-next v2 5/5] xfrm: merge dstopt and routing hdroff functions Florian Westphal
2021-06-14 9:55 ` Steffen Klassert [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=20210614095507.GV40979@gauss3.secunet.de \
--to=steffen.klassert@secunet.com \
--cc=fw@strlen.de \
--cc=herbert@gondor.apana.org.au \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).