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 2018-03-29
Date: Thu, 29 Mar 2018 11:23:23 -0400 (EDT) [thread overview]
Message-ID: <20180329.112323.723010861462079008.davem@davemloft.net> (raw)
In-Reply-To: <20180329072549.2880-1-steffen.klassert@secunet.com>
From: Steffen Klassert <steffen.klassert@secunet.com>
Date: Thu, 29 Mar 2018 09:25:45 +0200
> 1) Remove a redundant pointer initialization esp_input_set_header().
> From Colin Ian King.
>
> 2) Mark the xfrm kmem_caches as __ro_after_init.
> From Alexey Dobriyan.
>
> 3) Do the checksum for an ipsec offlad packet in software
> if the device does not advertise NETIF_F_HW_ESP_TX_CSUM.
> From Shannon Nelson.
>
> 4) Use booleans for true and false instead of integers
> in xfrm_policy_cache_flush().
> From Gustavo A. R. Silva
>
> Please pull or let me know if there are problems.
Also pulled, thank you.
prev parent reply other threads:[~2018-03-29 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 7:25 pull request (net-next): ipsec-next 2018-03-29 Steffen Klassert
2018-03-29 7:25 ` [PATCH 1/4] esp4: remove redundant initialization of pointer esph Steffen Klassert
2018-03-29 7:25 ` [PATCH 2/4] xfrm: mark kmem_caches as __ro_after_init Steffen Klassert
2018-03-29 7:25 ` [PATCH 3/4] esp: check the NETIF_F_HW_ESP_TX_CSUM bit before segmenting Steffen Klassert
2018-03-29 7:25 ` [PATCH 4/4] xfrm_policy: use true and false for boolean values Steffen Klassert
2018-03-29 15:23 ` 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=20180329.112323.723010861462079008.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).