From: Thomas Monjalon <thomas@monjalon.net>
To: Tiwei Bie <tiwei.bie@intel.com>
Cc: stable@dpdk.org, maxime.coquelin@redhat.com,
zhihong.wang@intel.com, dev@dpdk.org
Subject: Re: [dpdk-stable] [PATCH 2/2] examples/vhost: fix realloc failure
Date: Tue, 15 Jan 2019 02:56:39 +0100 [thread overview]
Message-ID: <8511626.MWUO4s5pd4@xps> (raw)
In-Reply-To: <20190114033444.13026-3-tiwei.bie@intel.com>
14/01/2019 04:34, Tiwei Bie:
> Fixes: ad0eef4d2203 ("examples/vhost: support multiple socket files")
> Cc: stable@dpdk.org
Please add some explanations about what was wrong.
About the title, do you mean "fix path allocation failure handling" ?
next prev parent reply other threads:[~2019-01-15 1:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190114033444.13026-1-tiwei.bie@intel.com>
2019-01-14 3:34 ` [dpdk-stable] [PATCH 1/2] vhost: fix memory leak on " Tiwei Bie
2019-01-14 10:20 ` Maxime Coquelin
2019-01-14 3:34 ` [dpdk-stable] [PATCH 2/2] examples/vhost: fix " Tiwei Bie
2019-01-14 10:20 ` Maxime Coquelin
2019-01-15 1:56 ` Thomas Monjalon [this message]
2019-01-15 6:53 ` Tiwei Bie
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=8511626.MWUO4s5pd4@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=stable@dpdk.org \
--cc=tiwei.bie@intel.com \
--cc=zhihong.wang@intel.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).