From: David Miller <davem@davemloft.net>
To: gustavo@embeddedor.com
Cc: borisp@mellanox.com, aviadye@mellanox.com, davejwatson@fb.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tls: Fix copy-paste error in tls_device_reencrypt
Date: Fri, 20 Jul 2018 12:13:21 -0700 (PDT) [thread overview]
Message-ID: <20180720.121321.2077860831497547427.davem@davemloft.net> (raw)
In-Reply-To: <20180718132741.GA9480@embeddedor.com>
From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
Date: Wed, 18 Jul 2018 08:27:41 -0500
> It seems that the proper structure to use in this particular
> case is *skb_iter* instead of skb.
>
> Addresses-Coverity-ID: 1471906 ("Copy-paste error")
> Fixes: 4799ac81e52a ("tls: Add rx inline crypto offload")
> Signed-off-by: Gustavo A. R. Silva <gustavo@embeddedor.com>
Applied, thank you.
prev parent reply other threads:[~2018-07-20 19:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 13:27 [PATCH] tls: Fix copy-paste error in tls_device_reencrypt Gustavo A. R. Silva
2018-07-20 19:13 ` 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=20180720.121321.2077860831497547427.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aviadye@mellanox.com \
--cc=borisp@mellanox.com \
--cc=davejwatson@fb.com \
--cc=gustavo@embeddedor.com \
--cc=linux-kernel@vger.kernel.org \
--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 NNTP newsgroup(s).