From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: AndyPei <andy.pei@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] Fix a memnory leak bug due to malloc unproperly.
Date: Thu, 13 Dec 2018 14:32:06 +0000 [thread overview]
Message-ID: <ce13d4a3-6181-3b85-c3f4-fd0b984d59c1@intel.com> (raw)
In-Reply-To: <1544725998-70149-1-git-send-email-andy.pei@intel.com>
Hi Andy,
The patch headline should say what the fix is for, e.g. raw/ifpga: fix
this or that.
If this is fixing a bug, a Fixes: tag should also be present, indicating
the original commit that introduced the issue. If this issue is present
in earlier releases, a Cc: stable@dpdk.org should also be added, to
ensure that older releases get this bugfix.
For more information, please refer to DPDK contribution guidelines:
https://doc.dpdk.org/guides/contributing/patches.html
On 13-Dec-18 6:33 PM, AndyPei wrote:
> Signed-off-by: AndyPei <andy.pei@intel.com>
> ---
--
Thanks,
Anatoly
next prev parent reply other threads:[~2018-12-13 14:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 18:33 AndyPei
2018-12-13 14:32 ` Burakov, Anatoly [this message]
2018-12-18 7:16 ` Xu, Rosen
2018-12-18 19:35 ` [dpdk-dev] [PATCH v2]/driver/raw/ifpga_rawdev: fix a memory leak bug in ifpga AndyPei
2018-12-19 7:16 ` Xu, Rosen
2018-12-19 8:42 ` Pei, Andy
2018-12-25 14:02 ` [dpdk-dev] [PATCH v3]/driver/raw/ifpga_rawdev: " AndyPei
2019-01-02 2:47 ` Zhang, Tianfei
2019-01-02 6:52 ` Xu, Rosen
2019-01-15 0:03 ` Thomas Monjalon
2019-01-15 5:38 ` [dpdk-dev] [DPDK] [PATCH v4] raw/ifpga: fix a typo and delete code of unused function Andy Pei
2019-01-16 11:26 ` Xu, Rosen
2019-01-17 5:26 ` [dpdk-dev] [DPDK] " Andy Pei
2019-01-17 5:36 ` Ye Xiaolong
2019-01-17 6:39 ` [dpdk-dev] [DPDK] raw/ifpga: fix a typo Andy Pei
2019-01-17 8:39 ` Xu, Rosen
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=ce13d4a3-6181-3b85-c3f4-fd0b984d59c1@intel.com \
--to=anatoly.burakov@intel.com \
--cc=andy.pei@intel.com \
--cc=dev@dpdk.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).