From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Xiaoguang Wang <wangxg.fnst@cn.fujitsu.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH 1/2] kernel/mem/lib/mem.c: fix compilation warnings
Date: Mon, 5 May 2014 14:13:25 +0800 [thread overview]
Message-ID: <53672C05.9020301@cn.fujitsu.com> (raw)
In-Reply-To: <1398674834-1643-1-git-send-email-wangxg.fnst@cn.fujitsu.com>
On 04/28/2014 04:47 PM, Xiaoguang Wang wrote:
> Functions declared in testcases/kernel/mem/include/_private.h is not
> implemented and used, so delete it.
>
> Signed-off-by: Xiaoguang Wang <wangxg.fnst@cn.fujitsu.com>
> ---
> testcases/kernel/mem/include/_private.h | 22 ----------------------
> testcases/kernel/mem/include/mem.h | 2 +-
> testcases/kernel/mem/lib/mem.c | 25 +++++++++++++++----------
> 3 files changed, 16 insertions(+), 33 deletions(-)
> delete mode 100644 testcases/kernel/mem/include/_private.h
Applied, thank you.
Wanlong Gao
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2014-05-05 6:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 8:47 [LTP] [PATCH 1/2] kernel/mem/lib/mem.c: fix compilation warnings Xiaoguang Wang
2014-04-28 8:47 ` [LTP] [PATCH 2/2] kernel/mem/lib/mem.c: do the necessary cleanup work Xiaoguang Wang
2014-04-28 10:56 ` Stanislav Kholmanskikh
2014-04-28 11:23 ` Xiaoguang Wang
2014-04-28 10:29 ` [LTP] [PATCH 1/2] kernel/mem/lib/mem.c: fix compilation warnings Stanislav Kholmanskikh
2014-05-05 6:13 ` Wanlong Gao [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=53672C05.9020301@cn.fujitsu.com \
--to=gaowanlong@cn.fujitsu.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=wangxg.fnst@cn.fujitsu.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.