From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
Lorenzo Colitti <lorenzo@google.com>,
Benedict Wong <benedictwong@google.com>,
Shannon Nelson <shannon.nelson@oracle.com>,
Antony Antony <antony@phenome.org>,
Eyal Birger <eyal.birger@gmail.com>,
Julien Floret <julien.floret@6wind.com>
Subject: Re: [PATCH ipsec v2] xfrm interface: fix memory leak on creation
Date: Thu, 4 Jul 2019 14:23:02 +0200 [thread overview]
Message-ID: <5c1126df-c6db-4f6c-4627-a4d37bfb609d@6wind.com> (raw)
In-Reply-To: <20190704102210.GK17989@gauss3.secunet.de>
Le 04/07/2019 à 12:22, Steffen Klassert a écrit :
[snip]
>
> Applied, thanks a lot!
>
I suppose that this patch will be queued for stable trees?
Regards,
Nicolas
prev parent reply other threads:[~2019-07-04 12:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 15:51 [PATCH ipsec v2] xfrm interface: fix memory leak on creation Nicolas Dichtel
2019-07-04 10:22 ` Steffen Klassert
2019-07-04 12:23 ` Nicolas Dichtel [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=5c1126df-c6db-4f6c-4627-a4d37bfb609d@6wind.com \
--to=nicolas.dichtel@6wind.com \
--cc=antony@phenome.org \
--cc=benedictwong@google.com \
--cc=davem@davemloft.net \
--cc=eyal.birger@gmail.com \
--cc=julien.floret@6wind.com \
--cc=lorenzo@google.com \
--cc=netdev@vger.kernel.org \
--cc=shannon.nelson@oracle.com \
--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