From: David Miller <davem@davemloft.net>
To: doronrk@fb.com
Cc: vakul.garg@nxp.com, davejwatson@fb.com, mmullins@fb.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2] tls: Fix improper revert in zerocopy_from_iter
Date: Sat, 28 Jul 2018 22:53:55 -0700 (PDT) [thread overview]
Message-ID: <20180728.225355.535868909090549115.davem@davemloft.net> (raw)
In-Reply-To: <20180726145936.3547913-1-doronrk@fb.com>
From: Doron Roberts-Kedes <doronrk@fb.com>
Date: Thu, 26 Jul 2018 07:59:34 -0700
> This series fixes the improper iov_iter_revert introcded in
> "tls: Fix zerocopy_from_iter iov handling".
>
> Changes from v1:
> - call iov_iter_revert inside zerocopy_from_iter
Series applied, thank you.
prev parent reply other threads:[~2018-07-29 7:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 14:59 [PATCH net-next v2 0/2] tls: Fix improper revert in zerocopy_from_iter Doron Roberts-Kedes
2018-07-26 14:59 ` [PATCH net-next v2 1/2] tls: Remove dead code in tls_sw_sendmsg Doron Roberts-Kedes
2018-07-26 14:59 ` [PATCH net-next v2 2/2] tls: Fix improper revert in zerocopy_from_iter Doron Roberts-Kedes
2018-07-29 5:53 ` 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=20180728.225355.535868909090549115.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=davejwatson@fb.com \
--cc=doronrk@fb.com \
--cc=mmullins@fb.com \
--cc=netdev@vger.kernel.org \
--cc=vakul.garg@nxp.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).