From: David Miller <davem@davemloft.net>
To: steffen.klassert@secunet.com
Cc: herbert@gondor.apana.org.au, netdev@vger.kernel.org
Subject: Re: pull request (net-next): ipsec-next 2019-07-05
Date: Fri, 05 Jul 2019 15:01:29 -0700 (PDT) [thread overview]
Message-ID: <20190705.150129.1445105190093420415.davem@davemloft.net> (raw)
In-Reply-To: <20190705084610.3646-1-steffen.klassert@secunet.com>
From: Steffen Klassert <steffen.klassert@secunet.com>
Date: Fri, 5 Jul 2019 10:46:01 +0200
> 1) A lot of work to remove indirections from the xfrm code.
> From Florian Westphal.
>
> 2) Fix a WARN_ON with ipv6 that triggered because of a
> forgotten break statement. From Florian Westphal.
>
> 3) Remove xfrmi_init_net, it is not needed.
> From Li RongQing.
>
> Please pull or let me know if there are problems.
Pulled, thanks.
prev parent reply other threads:[~2019-07-05 22:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 8:46 pull request (net-next): ipsec-next 2019-07-05 Steffen Klassert
2019-07-05 8:46 ` [PATCH 1/9] xfrm: remove init_tempsel indirection from xfrm_state_afinfo Steffen Klassert
2019-07-05 8:46 ` [PATCH 2/9] xfrm: remove init_temprop " Steffen Klassert
2019-07-05 8:46 ` [PATCH 3/9] xfrm: remove init_flags " Steffen Klassert
2019-07-05 8:46 ` [PATCH 4/9] xfrm: remove state and template sort indirections " Steffen Klassert
2019-07-05 8:46 ` [PATCH 5/9] xfrm: remove eth_proto value " Steffen Klassert
2019-07-05 8:46 ` [PATCH 6/9] xfrm: remove type and offload_type map " Steffen Klassert
2019-07-05 8:46 ` [PATCH 7/9] xfrm: fix bogus WARN_ON with ipv6 Steffen Klassert
2019-07-05 8:46 ` [PATCH 8/9] xfrm: remove empty xfrmi_init_net Steffen Klassert
2019-07-05 8:46 ` [PATCH 9/9] xfrm: remove get_mtu indirection from xfrm_type Steffen Klassert
2019-07-05 22:01 ` 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=20190705.150129.1445105190093420415.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.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).