From: Denis Kenzior <denkenz@gmail.com>
To: iwd@lists.01.org
Subject: Re: [PATCH 1/2] eap-ttls: Address mem leak reported by coverity
Date: Wed, 16 Oct 2019 15:50:36 -0500 [thread overview]
Message-ID: <126a6632-decd-8a04-7e78-d513bcf5965b@gmail.com> (raw)
In-Reply-To: <20191015173412.11810-1-tim.a.kourt@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 227 bytes --]
Hi Tim,
On 10/15/19 12:34 PM, Tim Kourt wrote:
> The issue has appeared in 6017dc573
> ---
> src/eap-ttls.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
Both applied, thanks.
Regards,
-Denis
prev parent reply other threads:[~2019-10-16 20:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 17:34 [PATCH 1/2] eap-ttls: Address mem leak reported by coverity Tim Kourt
2019-10-15 17:34 ` [PATCH 2/2] client: Address dbl free " Tim Kourt
2019-10-16 20:50 ` Denis Kenzior [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=126a6632-decd-8a04-7e78-d513bcf5965b@gmail.com \
--to=denkenz@gmail.com \
--cc=iwd@lists.01.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