All of lore.kernel.org
 help / color / mirror / Atom feed
From: <wang.yong19@zte.com.cn>
To: <thomas@monjalon.net>
Cc: <dev@dpdk.org>, <hemant.agrawal@nxp.com>, <beilei.xing@intel.com>,
	<wenzhuo.lu@intel.com>, <john.griffin@intel.com>
Subject: 答复: Re:  [PATCH v2 1/4] net/dpaa: add null point check and fix mem leak
Date: Mon, 22 Jan 2018 10:53:17 +0800 (CST)	[thread overview]
Message-ID: <201801221053179672021@zte.com.cn> (raw)
In-Reply-To: <3290561.5TofqmsUDE@xps>

Hi,
I've sent this patch again and it is accepted.
The other 3 pathes have no conflict with the latest master version and the titles have described the modification of the patches.
So I need not send the patches for v3, right?




------------------origin------------------
From ： <thomas@monjalon.net>;
to ：wang.yong19@zte.com.cn;
cc： <dev@dpdk.org>; <hemant.agrawal@nxp.com>; <beilei.xing@intel.com>; <wenzhuo.lu@intel.com>; <john.griffin@intel.com>;
date ：2018-01-18 07:00
subject ：Re: [dpdk-dev] [PATCH v2 1/4] net/dpaa: add null point check and fix mem leak
Hi,

Please could you rebase on master and keep the acked already given?
Please use --in-reply-to to keep v3 in the same thread as v2.

Titles are the same for every patches.
Are they all fixing a NULL pointer check and a mem leak?
More details in the commit message may help.

If they are fixes, a tag Fixes: may help for backports.

Thanks

  reply	other threads:[~2018-01-22  2:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-20 10:23 [PATCH v2 1/4] net/dpaa: add null point check and fix mem leak Yong Wang
2017-12-20 10:23 ` [PATCH v2 2/4] net/i40e: " Yong Wang
2017-12-27  6:41   ` Xing, Beilei
2017-12-20 10:23 ` [PATCH v2 3/4] net/e1000: add null point check for rte_zmalloc Yong Wang
2017-12-20 10:23 ` [PATCH v2 4/4] crypto/qat: add null point check and fix mem leak Yong Wang
2017-12-20 12:22   ` Trahe, Fiona
2017-12-20 12:58 ` [PATCH v2 1/4] net/dpaa: " Shreyansh Jain
2018-01-17 23:00 ` Thomas Monjalon
2018-01-22  2:53   ` wang.yong19 [this message]
2018-01-22  7:51     ` 答复: " Thomas Monjalon

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=201801221053179672021@zte.com.cn \
    --to=wang.yong19@zte.com.cn \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=john.griffin@intel.com \
    --cc=thomas@monjalon.net \
    --cc=wenzhuo.lu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.