From: David Miller <davem@davemloft.net>
To: jakub.kicinski@netronome.com
Cc: netdev@vger.kernel.org, oss-drivers@netronome.com,
alexei.starovoitov@gmail.com
Subject: Re: [PATCH net-next 00/11] nfp: tls: fixes for initial TLS support
Date: Mon, 08 Jul 2019 20:39:10 -0700 (PDT) [thread overview]
Message-ID: <20190708.203910.687771443983336568.davem@davemloft.net> (raw)
In-Reply-To: <20190709025318.5534-1-jakub.kicinski@netronome.com>
From: Jakub Kicinski <jakub.kicinski@netronome.com>
Date: Mon, 8 Jul 2019 19:53:07 -0700
> This series brings various fixes to nfp tls offload recently added
> to net-next.
Series applied, thanks.
prev parent reply other threads:[~2019-07-09 3:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 2:53 [PATCH net-next 00/11] nfp: tls: fixes for initial TLS support Jakub Kicinski
2019-07-09 2:53 ` [PATCH net-next 01/11] nfp: tls: ignore queue limits for delete commands Jakub Kicinski
2019-07-09 2:53 ` [PATCH net-next 02/11] nfp: tls: move setting ipver_vlan to a helper Jakub Kicinski
2019-07-09 2:53 ` [PATCH net-next 03/11] nfp: tls: use unique connection ids instead of 4-tuple for TX Jakub Kicinski
2019-07-09 2:53 ` [PATCH net-next 04/11] nfp: ccm: increase message limits Jakub Kicinski
2019-07-09 2:53 ` [PATCH net-next 05/11] nfp: tls: count TSO segments separately for the TLS offload Jakub Kicinski
2019-07-09 2:53 ` [PATCH net-next 06/11] net/tls: don't clear TX resync flag on error Jakub Kicinski
2019-07-09 2:53 ` [PATCH net-next 07/11] nfp: tls: don't leave key material in freed FW cmsg skbs Jakub Kicinski
2019-07-09 2:53 ` [PATCH net-next 08/11] net/tls: add missing prot info init Jakub Kicinski
2019-07-09 2:53 ` [PATCH net-next 09/11] nfp: tls: avoid one of the ifdefs for TLS Jakub Kicinski
2019-07-09 2:53 ` [PATCH net-next 10/11] nfp: tls: undo TLS sequence tracking when dropping the frame Jakub Kicinski
2019-07-09 2:53 ` [PATCH net-next 11/11] net/tls: fix socket wmem accounting on fallback with netem Jakub Kicinski
2019-07-09 3:39 ` 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=20190708.203910.687771443983336568.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexei.starovoitov@gmail.com \
--cc=jakub.kicinski@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.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).